Problem has been solved by using two different keys for the
idempotentConsumer and idempotentRepository then setting
readLockRemoveOnCommit=true so once the readlock has been released by the
node consuming the file, it is removed from the repository. This leaves the
idempotentConsumer to record and handle any duplicates.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Skip-duplicate-for-idempotent-file2-component-tp5788485p5788562.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to