camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: deadLetterHandleNewException(false) seems to not work as expected
Date Sun, 10 Jan 2016 11:28:40 GMT

This is as expected. The option deadLetterHandleNewException is only
for new errors happening while the dead letter channel is processing
the message.

Your code just routes to a log as the dead letter channel and there is
no exception thrown.

See this unit test for an example

On Wed, Dec 16, 2015 at 11:32 AM, lchdev <> wrote:
> I am trying to use the option /deadLetterHandleNewException(false)/ in order
> to have any new Exception occurring during the dead letter processing be
> propagated back. Unfortunately, when doing so, it seems that the dead letter
> channel propagates back the original exception as well, even if the
> DeadLetterChannel succeeded. This is definitely not the behavior that I
> expected.
> This has been tested with Camel 2.15.3 and 2.16.1, both behave in the same
> (unexpected) way. Am I misconfiguring or misusing something ? Or is it a bug
> ? Here is a simple route (Java DSL) that is sufficient to illustrate the
> behavior:
> Sending a message to this route will trigger an Exception that will be
> propagated back to the producer, even if we can see in the logs that the
> DeadLetterChannel has successfully *handled* the exception.
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
----------------- @davsclaus
Camel in Action 2:

View raw message