On Mon, Feb 1, 2010 at 4:33 AM, Raster3 <[email protected]> wrote: > > Thanks. > I am just trying to understand. > If my dead letter queue is just a jms queue and i dont use the camel error > handler does camel give any other value add? >
The DL queue in the JMS broker is for *JMS only* where as Camel DL is for all kind of messages. For example you can use it for file based messages as well. If all you need is JMS then I suggest to stick to what the JMS broker offers for error handling. You are already familiar with that and how to use it. And I assume you have procedures for how to monitor it and handle those failed messages when something goes wrong. > R > > > > willem.jiang wrote: >> >> Hi, >> >> First Camel dead letter channel is a generate channel. You can not only >> store the message into a dead letter queue, but also any other Camel >> endpoints(such as sead, direct or file). >> >> Second, Camel dead letter channel has some advance features which are >> inherited from error handler[1], you can user the try... catch and >> onwhen, onException to deal with different error message. >> >> [1]http://camel.apache.org/error-handler.html >> >> Willem >> >> >> Raster3 wrote: >>> Hi, >>> >>> I was looking at this http://camel.apache.org/dead-letter-channel.html >>> Previously I have worked with JMS dead letter / error queues using >>> weblogic. >>> >>> In Weblogic an error queue is something one configures and associates >>> with a >>> queue using the weblogic console or using JMX . Depending on the >>> configuration after a time period or number of retries the message is >>> moved >>> to the dead letter queue. >>> >>> Can you please elaborate on what exactly is the value add of camel in >>> this >>> context. >>> >>> R >> >> >> > > -- > View this message in context: > http://old.nabble.com/Dead-Letter-Queue-tp27393562p27399328.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
