camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Persistent Message Headers on deadLetterChannel
Date Wed, 19 Jan 2011 13:02:10 GMT
On Wed, Jan 19, 2011 at 1:42 PM, James Morgan <james.morgan.e@gmail.com> wrote:
> Hi,
>
> Im having a problem when using a deadLetterChannel inside one of my routes.
>
> The messages are being routed to the error handler correctly however when
> they reach it, all the headers of the message have been lost.
>
> Is this expected behaviour or am I doing some thing wrong?
>

If you use JMS then its on purpose as there is a limitation when using JMS.
The JMS broker do have build-in error handling themself, so its often
better to use their error handling when consuming from JMS queues.
We will revisit this in Camel 3.x


> Camel Version 2.5.0
>
> Dead Letter Channel:
>
> errorHandler(deadLetterChannel(deadLetterUri)
>  .maximumRedeliveries(0)
> .retriesExhaustedLogLevel(LoggingLevel.ERROR)
>  .retryAttemptedLogLevel(LoggingLevel.WARN)
> .log("com.my.employer.Failure")
>  .loggingLevel(LoggingLevel.ERROR)
> .logStackTrace(true)
> .useOriginalMessage()
>  );
>
> Cheers
>



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message