Issue: https://issues.apache.org/jira/browse/AMQ-4634
Resolved
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-XA-JBoss-6-1-problem-tp4669324p4669473.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ActiveMQSession creates a new local transaction because there isn't an XA trx
in the trasactioncontext.
Logs:
/09:22:32,326 DEBUG [org.apache.activemq.TransactionContext] Start: <
formatId=131076, gtrid_length=29, bqual_length=28,
tx_uid=0:c0a80ad8:126a:51e5393b:43, node_name=1,
branch_uid=0:f
I've tried to reproduce this without calling the stateless ejb but it works
well.
The ActiveMQSession class should retain the original transactionContext, as
you mentioned.
I'll create an issue.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-XA-JBoss-6-1-problem
Hi,
We have some XA problems using ActiveMQ ra within Jboss 6.1 (tested in v5.6,
v5.7 and v5.8 with the same result).
The ActiveMQ is working in standalone mode (outside jboss).
There are two resources involved in the transaction (activemq and db), both
definied as xa resources.
ActiveMQ does a tr
