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.

Reply via email to