Hi Maybe you do some custom processing or something where you dont close the file / input stream etc.
Also do you need the read lock at all? If you are the only one reading those files you can then turn that off. Also test with newer Camel versions On Tue, Jan 24, 2017 at 9:38 PM, GaryLeeMills <[email protected]> wrote: > Hello, > > 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/camel-pollEnrich-API-not-working-properly-Camel-2-15-leaves-file-locks-on-aggregation-uri-path-tp5793038.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
