Clause, thank you so much, I'm working somewhat. Can I ask you if there are
any known issues with the pollEnrich API in that it does not release the
file locks ? it is always on the pollenrichment path.
<pollEnrich strategyRef="navSeaAggregationStrategy"
uri="{{CMAS_LPD22_MPDE1A}}?fileName=CMAS_LPD22_MPDE1A_PG2.csv&delay=2000"
timeout="60000" />
It leaves a messy file system, and then any additional events do not work
until the locks are removed. ???? the PG2 is always on the pollEnrich path
as the appended file or data.
└── tobeprocessed
│ ├── LPD221A
│ │ ├── .camel
│ │ │ ├── CMAS_LPD22_MPDE1A_PG1.csv
│ │ │ └── CMAS_LPD22_MPDE1A_PG2.csv
│ │ ├── CMAS_LPD22_MPDE1A_PG2.csv
│ │ └── CMAS_LPD22_MPDE1A_PG2.csv.camelLock
│ ├── LPD221B
│ │ ├── .camel
│ │ │ ├── CMAS_LPD22_MPDE1B_PG1.csv
│ │ │ └── CMAS_LPD22_MPDE1B_PG2.csv
│ │ ├── CMAS_LPD22_MPDE1B_PG2.csv
│ │ └── CMAS_LPD22_MPDE1B_PG2.csv.camelLock
│ ├── LPD222A
│ │ ├── .camel
│ │ │ ├── CMAS_LPD22_MPDE2A_PG1.csv
│ │ │ └── CMAS_LPD22_MPDE2A_PG2.csv
│ │ ├── CMAS_LPD22_MPDE2A_PG2.csv
│ │ └── CMAS_LPD22_MPDE2A_PG2.csv.camelLock
│ ├── LPD222B
│ │ ├── .camel
│ │ │ ├── CMAS_LPD22_MPDE2B_PG1.csv
│ │ │ └── CMAS_LPD22_MPDE2B_PG2.csv
│ │ ├── CMAS_LPD22_MPDE2B_PG2.csv
│ │ └── CMAS_LPD22_MPDE2B_PG2.csv.camelLock
--
View this message in context:
http://camel.465427.n5.nabble.com/pollEnrich-and-variable-file-names-time-stamp-tp5792827p5793037.html
Sent from the Camel - Users mailing list archive at Nabble.com.
