Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 67668 invoked from network); 15 Mar 2011 21:28:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Mar 2011 21:28:08 -0000 Received: (qmail 63527 invoked by uid 500); 15 Mar 2011 21:28:08 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 63496 invoked by uid 500); 15 Mar 2011 21:28:08 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 63481 invoked by uid 99); 15 Mar 2011 21:28:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Mar 2011 21:28:07 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of akarpe@fusesource.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Mar 2011 21:28:02 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1PzbmH-0003XC-2X for users@camel.apache.org; Tue, 15 Mar 2011 14:27:41 -0700 Date: Tue, 15 Mar 2011 14:27:41 -0700 (PDT) From: Ashwin Karpe To: users@camel.apache.org Message-ID: <1300224461072-3723179.post@n5.nabble.com> In-Reply-To: <1300131812861-3595142.post@n5.nabble.com> References: <1300131812861-3595142.post@n5.nabble.com> Subject: Re: ActiveMQ stuck message using JTA Transactions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, It is quite unclear why/what you are really trying to do. First, When you say PROPAGATION_REQUIRED, you pass the transaction context along the route hoping that somewhere along the way following proper processing, the exchange will come back in a state where a commit/rollback can be done on this transaction. But halfway through, (Note you are using direct: an in-memory component), you stomp the original transaction to create a new transaction without sending back an success/fail on the original leg. This is what is causing problems you are seeing, I believe. If you create 2 distinct routes, not using direct but rather (http, mina/netty, jms) then you should be able to create 2 separate and distinct routes where the traction boundary does not carry forward beyond the transport producer. Then I believe it should work. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com Blog: http://opensourceknowledge.blogspot.com --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/ActiveMQ-stuck-message-using-JTA-Transactions-tp3595142p3723179.html Sent from the Camel - Users mailing list archive at Nabble.com.