The idempotent repository can be a database table. You define a key for the message and that prevents the file from being consumed on multiple nodes. You should still move the file out of the directory when you are done processing.
Thanks, Joe > On Oct 7, 2016, at 10:19 AM, sian <sianfwebs...@gmail.com> wrote: > > I am using camel over a clustered environment and want to use a readlock on > my file consumer endpoint. The only cluster safe readlock is the idempotent > readlock however this requires an idempotentRepository to be set on the file > uri. > > I use an idempotent consumer within the route which moves any duplicate > files to an error folder and logs the error to a specific file. > > Is there a way to use this idempotent consumer with the idempotent readlock? > Or a way to set the idempotentRepository in the file component to not skip > the duplicates so they are picked up by the idempotent consumer in the route > instead? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Skip-duplicate-for-idempotent-file2-component-tp5788485.html > Sent from the Camel - Users mailing list archive at Nabble.com.
