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
Hi Joe,
Thanks for the response.
I am using a database table as the repository for the idempotent consumer as
you described. My issue is that if I use the idempotentRepository file
component (as required to use the idempotent readlock) then I cannot find a
way to move the file out of the director
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 wrote:
>
>
