Idempotency – Time Out?
The idempotent router allows you to make sure that multiple messages with the same ID are not re-processed. While comfortable, the router needs to store the list of IDs somewhere and this list is only going to grow as time passes … unless the list is purged at some point.
Taking a look at the code for the Idempotent Receiver class, you can see that the createMessageIdStore() method has the following line of code:
setEntryTTL(60 * 5);
which shows that the messages have a time-to-live value of 300 seconds.
If you enjoyed this post, make sure you subscribe to my RSS feed!
Tags: createMessageIdStore, idempotent router, setEntryTTL, timeout