activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: ActiveMQ XA JBoss 6.1 problem
Date Thu, 22 Aug 2013 10:22:28 GMT
if you can patch ActiveMQSession that will do it.
Apply this change:
http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/ActiveMQSession.java?r1=1504279&r2=1504278&pathrev=1504279

On 21 August 2013 17:21, juanlopez <juan.lopezutn@gmail.com> wrote:
> Hi I have the same problem in this post
> ------------------------------------------------
> 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,
> ----------------------------------------------------------------
>
> I see jira related this post https://issues.apache.org/jira/browse/AMQ-4634
> but I have version 5.6 Is possible move this patch from 5.8 to 5.6.  If I
> only update this class ActiveMQSession is enough for resolved this issue,
> But I don't know this solution is only availabel for version 5.8 and not for
> 5.6.
> Can you help me about this ?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-XA-JBoss-6-1-problem-tp4670555.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.



-- 
http://redhat.com
http://blog.garytully.com

Mime
View raw message