On Wed, Jan 19, 2011 at 2:07 PM, James Morgan <[email protected]> wrote: > Would a possible work around be to then, on error send to a SEDA queue which > is then routed to a final jms error queue? >
No > Or is the fact the original message is on JMS which is where the limitation > lies? > Yes (and partly due the Camel routing engine, which we will optimize / refactor in Camel 3.0) > Cheers > > > On 19 January 2011 13:02, Claus Ibsen <[email protected]> wrote: > >> On Wed, Jan 19, 2011 at 1:42 PM, James Morgan <[email protected]> >> 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: [email protected] >> Web: http://fusesource.com >> Twitter: davsclaus >> Blog: http://davsclaus.blogspot.com/ >> Author of Camel in Action: http://www.manning.com/ibsen/ >> > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
