Hi Yeah I will do that. I have observed that on Camel 2.4 the error actually comes from the Splitter exactly like in this post:
http://camel.465427.n5.nabble.com/File-can-t-be-moved-or-deleted-on-Windows-td512484.html#a512484 <route> <from uri="file:data/in2?move=backup&moveFailed=error" /> <split> <tokenize token="," /> <to uri="mock:test" /> </split> </route> This will fail. On Camel 2.5 this seems to be working, but when I introduce an Aggregator it fails. It sometimes fails renaming a file to "backup" dir. It never releases a .camelLock file on the first file of the batch. -- View this message in context: http://camel.465427.n5.nabble.com/Processed-file-being-read-again-and-is-empty-tp3256771p3258701.html Sent from the Camel - Users mailing list archive at Nabble.com.