Hi Yeah you gotta be more careful when using the AggregationStrategy because you need to ensure the on completions is preserved. So it may actually matter whether or not you return oldExchange or newExchange.
Can you post your AggregationStrategy implementation? But if you do not need the read locks at all then just set it to readLock=none on the file endpoint, and you wont have issues with .camelLock files. On Tue, Nov 9, 2010 at 3:01 PM, Andreas A. <[email protected]> wrote: > > Fails in 2.5 also, as well as leaving the camelLock file behind. But could > this have anything to do with the aggregator having control over the file > that the original route is trying to move, or should Camel be able to handle > this? Would wiretapping over into the queue do any difference? > -- > View this message in context: > http://camel.465427.n5.nabble.com/Processed-file-being-read-again-and-is-empty-tp3256771p3256862.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
