camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ashwin Karpe <aka...@fusesource.com>
Subject Re: ActiveMQ stuck message using JTA Transactions
Date Tue, 15 Mar 2011 21:27:41 GMT
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.

Mime
View raw message