A little further digging. I added some debugging output to
incrementRedeliveryCounter and found the CamelRedeliveryCounter header is
missing on the redelivery attempt, I see the following:
2014-10-16 09:01:48,976 [CamelJettyClient(0x106898e3)-88] DEBUG
camel.processor.RedeliveryErrorHandler in in
I added some debugging output into RedeliveryPolicy.java and confirmed that
it's not correctly incrementing redeliveryCounter.
2014-10-16 08:29:16,280 [CamelJettyClient(0x533bbc89)-59] DEBUG
camel.processor.RedeliveryPolicy in shouldRedeliver, *redeliveryCounter = 1*
2014-10-16 08:29:16,280 [Came
Thanks Charles.
I have a doTry inside route2 that has handled=false, and the *onException in
route1 is firing the redelivery*. The only issue I have is that it
redelivers an infinite number of times until the route succeeds instead of
twice. It appears to be *forgetting the current retry count
Hi Nathan,
When you use the doTry, doCatch processors, they will handle the exceptions
instead of the interceptor (= onException).
Regards,
On Wed, Oct 15, 2014 at 9:36 PM, nathanwray wrote:
> Hi all;
>
> I have a global onException defined that I hoped would let me retry an
> entire route tw
