You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Ayache Khettar <ay...@googlemail.com> on 2014/10/23 12:14:33 UTC

ErrorHandler and RetryPolicy

Hi

I am doing a bit of research on the best way to implement an Asynchronous
Delayed Redelivery. I am well aware that if you set the
*AsyncDelayedRedelivery
option *on the retry delivery, Camel will use a scheduler so an
asynchronous thread will perform the redelivery. This ensure no thread is
blocked while waiting for redelivery.

Our system in some cases, redeliveries are scheduled for hours or days, I
am wondering if the above mechanism (Asynchronous redelivery) is sufficient
for our use cases. Bear in mind the system will be handling around 500
messages per second and if one of the third party system endpoint isn't
available, the number of messages scheduled for redelivery could grow to a
massive number. I guess my question is how does Camel redelivery scheduler
works? Where does it store the redeliveries details, in memory, file based
system? And can it be configured?

Any help or direction on how best to implement a scalable solution for
redelivery for high throughput system is very much appreciated.

kind regards,

Ayache