On Fri, Feb 4, 2011 at 3:36 PM, waterback <[email protected]> wrote: > > Hi Claus, > > i know this is a rather old post, but i have a question referring to your > response: > > Does this mean, that if you have - lets say - 10 transacted routes, which > all use the same RedeliveryHandler > that if even if you don't have an exception that triggers a redelivery, > those 10 routes won't get worked on in parallel? > > Or does this only come into effect when there's an exception? >
The redelivery is scheduled in Camel 2.4 onwards, and you can use the asyncDelayed option to allow asynchronous redelivery tasks. See here: http://camel.apache.org/delayer.html. The same options is avail on error handler. Then if there is a redelivery then its just add to the thread pool and the thread can move on processing the next message. Then its up to the redelivery thread pool how many redeliveries you can process concurrently. Currently its configured to allow 10 threads in that pool. We should offer an option so you can configure this as well. I will create a JIRA for that. > Thx, > Martin > -- > View this message in context: > http://camel.465427.n5.nabble.com/Message-blocks-route-until-all-redelivery-attempts-are-exhausted-tp472319p3371056.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
