btw: in the jboss logs or on the console, do you see: .... WARN [org.apache.activemq.ra.ServerSessionImpl:0] (default-threads - 2) Local transaction had not been commited. Commiting now.
On 15 July 2013 21:10, gastonscapusio <don_ga...@hotmail.com> wrote: > 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. -- http://redhat.com http://blog.garytully.com
