It's an in-memory solution. For the requirement you described, we are using the scheduled message delivery option provided by ActiveMQ [1]. Unfortunately it's a bit more complicated to set it up, than the Camel provided in-memory redelivery - but no rocket science...
[1] http://activemq.apache.org/delay-and-schedule-message-delivery.html Best, Christian ----------------- Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Mon, Oct 27, 2014 at 10:12 AM, akcameluser <ayache.khet...@gmail.com> wrote: > Hi > > I have posted this on camel user and I didn't get any feedback, hoping to > get some here. 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 > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/ErrorHandler-and-RetryPolicy-tp5758074.html > Sent from the Camel Development mailing list archive at Nabble.com. >
