Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 don_gatos@hotmail.com does not designate 216.139.250.139 as permitted sender)
Date: Mon, 15 Jul 2013 13:10:38 -0700 (PDT)
From: gastonscapusio <don_gatos@hotmail.com>
To: users@activemq.apache.org
Message-ID: <1373919038707-4669324.post@n4.nabble.com>
Subject: ActiveMQ XA JBoss 6.1 problem
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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 trx commit when there is a transaction timeout
(/EJBTransactionRolledbackException/). In this way we are losing messages
when there is any timeout.
We have seen that the activemq connections are enlist in XA.
The attribute /transactionContext/ from /ActiveMQSession/ class has the
global transaction reference (xid) before calling the MDB
(/messageListener.onMessage(message)/).
When the timeout is reached and the RuntimeException is throwned, the
transactionContext losed the xid reference.
Later, when ActiveMQSession call the method
/transactionContext.isInXATransaction()/ the result is false because there
is no xid reference.

This situation only happened when the MDB calls other EJB (Stateless) with
CMT - /TransactionAttributeType.REQUIRES_NEW/, and the exception is throwed
inside the Stateless.

Any ideas?

Regards,
Gaston


--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-XA-JBoss-6-1-problem-tp4669324.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.