On Tue, May 4, 2010 at 7:53 PM, gnanda <[email protected]> wrote: > > Hi All, > I upgraded my code from smx4.0 to smx4.2 to get better error handling > feature with transaction support. > > But looks like it is not doing as I was expecting. I could get onException > block works with transactional route. But if the transaction fail at the > end, it does not go to DeadLetterQueue which I configured in > activemq-broker.xml file. After reading the documents I got to know that > transactionalErrorHandler ignores DLQ setting. >
Yes it does. If the message was set to rollback or an exception was not handled, then the JMS will receive this error. And if you have JMS Broker configured to move to DLQ after X attempts it will do so. I assume you may have configured JMS Broker to move to DLQ after 6 attempts, and then you have Camel configured to retry X times as well. That gives you total 6 * X times. > We cannot afford loosing any message in our scenario. > Let the JMS Broker handle the redelivery and move to DLQ after X attempts. It has various options to configure this. > Is there any way I could configure the transactionErrorHandler to reroute > the message to any other queue (example "errorQ") in case of failure? > > Please help. > > -- > View this message in context: > http://old.nabble.com/smx4%3Acamel2.2-transactional-error-handling-tp28450957p28450957.html > Sent from the ServiceMix - User 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
