Thank you for the explanation.
From: Claus Ibsen-2 [via Camel]
[mailto:ml-node+s465427n5748500...@n5.nabble.com]
Sent: Sunday, March 9, 2014 10:02 AM
To: bocamel
Subject: Re: Dead letter queue and onException
Hi
This is by design. If onException is triggered then it does it work,
an
Hi
This is by design. If onException is triggered then it does it work,
an not the DLC etc.
If you want to do some routing before moving to a DLC, then use a
route as the DLC, and use direct:todlc as endpoints so you route to
your route using direct.
On Wed, Jan 22, 2014 at 8:19 PM, bocamel wro
Hi Claus, Thank you for your response. The version being tested is 2.12.2.
--
View this message in context:
http://camel.465427.n5.nabble.com/Dead-letter-queue-and-onException-tp5746362p5746402.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Charles, thank you very much for the response. I assume what you meant
was to reference the DLC in because the Spring DSL does not allow
definition within . I tried to move the
errorHandlerRef in the . It did not help. The failed message was
only written to the dead queue if the error was
What Camel version do you use?
On Wed, Jan 22, 2014 at 8:19 PM, bocamel wrote:
> It seems that whenever an error is caught by onException, regardless whether
> handled is set to true or false, the failed message would not be written to
> the dead letter queue. Here is a sample project to demonst
Can you move the DLC definition inside the please
and make a test ?
On Wed, Jan 22, 2014 at 8:19 PM, bocamel wrote:
> It seems that whenever an error is caught by onException, regardless
> whether
> handled is set to true or false, the failed message would not be written to
> the dead letter
