I would like to take back my statement regarding "The transactional error handling is working". It is not working in all the scenarios.
I have a call to external web service as my target endpoint. If the target endpoint receives the message but returns a soap fault or any error then the message is routed to DLQ but many other exceptions like java.net.ConnectException (when external web service is down) or nullpointerException( if the incoming soap message is not in expected format) then the message is not getting routed to DLQ For the time being I am using onException block to route to errorQ not to loose the message gnanda wrote: > > Hi All, > looks like the error handling is working. I had a bug in my code and that > was raising exception, that exception was not re-routing it to DLQ. It was > routing to Q attached to onException() route. > If I have any exception on exchanging with external endpoint then it is re > routing it to DLQ > > Thank you all > > The error handling is working > > gnanda 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. >> >> We cannot afford loosing any message in our scenario. >> >> 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-tp28450957p28512482.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
