Hi It may also matter what os your use. For example windows is much more prone to not being able to delete files from Java even though the JVM was the owner of the file handle.
And you can also try to make a small example where you only do poll enrich and then maybe a empty processor or something to avoid reading the file to see if those lock files are still there or not. On Thu, Jan 26, 2017 at 9:46 PM, GaryLeeMills <[email protected]> wrote: > thanks again Claus > > yeah, I've already looked at that and unfortunately that's not it. bummer, > would've been an easy fix. > > yes, I really do not need the lock because am the only one reading it. I > will give this a try. > > I am upgrading also, I'll do this first, since I am using JBoss Fuse OSGI > container... I am moving to > <jboss.fuse.bom.version>6.2.1.redhat-084</jboss.fuse.bom.version> > this release and version. It was recommended by Apache Fuse support. I am > not sure right now what camel core release is bundled here but, going to > give it a try. > > thanks so much, I'll let you know the outcome! > > > > -- > 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-tp5793038p5793092.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
