Return-Path: Delivered-To: apmail-servicemix-users-archive@www.apache.org Received: (qmail 80346 invoked from network); 4 May 2010 17:53:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 May 2010 17:53:45 -0000 Received: (qmail 5265 invoked by uid 500); 4 May 2010 17:53:45 -0000 Delivered-To: apmail-servicemix-users-archive@servicemix.apache.org Received: (qmail 5240 invoked by uid 500); 4 May 2010 17:53:45 -0000 Mailing-List: contact users-help@servicemix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@servicemix.apache.org Delivered-To: mailing list users@servicemix.apache.org Received: (qmail 5232 invoked by uid 99); 4 May 2010 17:53:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 17:53:45 +0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=AWL,FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 17:53:39 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1O9MJ4-0005c4-0H for users@servicemix.apache.org; Tue, 04 May 2010 10:53:18 -0700 Message-ID: <28450957.post@talk.nabble.com> Date: Tue, 4 May 2010 10:53:18 -0700 (PDT) From: gnanda To: users@servicemix.apache.org Subject: smx4:camel2.2 transactional error handling MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: gitanjali.nanda@phaseforward.com 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-tp28450957p28450957.html Sent from the ServiceMix - User mailing list archive at Nabble.com.