On Wed, Aug 22, 2012 at 1:38 PM, sarfaraj <sarfarajsay...@gmail.com> wrote: > Hi, > > I observed onException (using redeliveryPolicy) retry particular processor > in which exception occurred. Can it be retry from start ? > > like if we have 3 processor doing something (say ...processor 1, processor > 2, processor 3) > > if exception occurred at processor 2 then it's retrying for processor 2 > only. > > how do we configure to retry from processor 1 ? > > Any suggestion/thoughts ? >
This is by design to retry at the point of failure. If you want to start all over then if you use JMS etc as input, you can use transaction, and have the JMS broker redeliver the message to Camel again. An alternative in Camel is to use a DeadLetterChannel error handler, and send the message into the route again using a seda endpoint or something. Mind about endless looping if the error occurs all the time. And you would need to enable the use original message option. This has been talked about before on this @user forum, you may find the thread with code samples. > /Sarfaraj > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/redeliveryPolicy-How-can-we-retry-from-start-of-the-route-in-case-of-exception-occurred-inbetween-of-tp5717848.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
