it to:
And the issue went away, it now redelivers twice and then fails as designed.
--
View this message in context:
http://camel.465427.n5.nabble.com/onException-and-doTry-tp5757602p5757629.html
Sent from the Camel - Users mailing list archive at Nabble.com.
DEBUG
camel.processor.RedeliveryPolicy maxRedeliveries is 2, returning true
...
and so on
--
View this message in context:
http://camel.465427.n5.nabble.com/onException-and-doTry-tp5757602p5757627.html
Sent from the Camel - Users mailing list archive at Nabble.com.
count*. I'm not sure
that's related to the inner route's doTry or not. Is the route count
threadlocal, and the thread is changing? I'm not sure what the underlying
mechanism is.
--
View this message in context:
http://camel.465427.n5.nabble.com/onException-and-doTry-tp
; at
>
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> at
>
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> at java.lang.Thread.run(Thread.java:745)
>
> 2014-10-15 15:00:14,474 [Camel (camel-1) t
15:00:14,474 [Camel (camel-1) thread #10 -
ErrorHandlerRedeliveryTask] DEBUG route2 a debugging message here from
route2
Any thoughts?
--
View this message in context:
http://camel.465427.n5.nabble.com/onException-and-doTry-tp5757602.html
Sent from the Camel - Users mailing list archive
On Fri, Dec 11, 2009 at 11:21 PM, Dragisa Krsmanovic
wrote:
> In this route, although message, correctly, does not get to mock:end, it
> does not seem to go to mock:error either.
>
doTry .. doCatch .. doFinally does NOT use regular error handling.
Its in fact its own little error handler where yo
In this route, although message, correctly, does not get to mock:end, it
does not seem to go to mock:error either.
from("seda:start")
.onException(Exception.class)
.handled(true)
.redeliveryDelay(10)
.maximumRedeliveries(2)
.retryAttemptedLogLevel(LoggingLevel.WARN)
