activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Gies <>
Subject Re: XAResourceRecovery for ActiveMQ on JBoss
Date Thu, 10 Dec 2009 21:33:47 GMT
Hi there, 

I am working on some JBoss integration as well. I don't understand the comment on 
"making the RA XA compatible". At the end of the day it depends on hon how you do the 
transaction management and define the connection factories. 

A non-tx-connection-factory defined in the jboss-ds does not support transactions, a 
tx-connection without the xa-transaction element does only support local transactions, 
a tx-connection with the xa-connection element support local and xa-transactions.

As far as I am reading the code correctly, the RA recognizes the transaction context correctly
and encapsulates local AND xa transactions in org.apacheactivemq.TransactionContext.

I *think* you only need to use the XA capable connection factory if you want to register the

CF manually and not have the RA do the transaction management. So, either you are using the

RA with the correct definition in the ds-definition file OR you are using a XA capable CF.

Could you elaborate a bit on your use case in case I am missing something, perhaps there is

a test case to try ?

Best regards

On Dec 9, 2009, at 4:27 PM, jp.belanger wrote:

> rajdavies wrote:
>> On 5 Nov 2009, at 05:58, Roland T. Lichti wrote:
>>> I'm willing to do try it - but only if there is a chance to get it  
>>> back
>>> into SVN (I don't need to be the committer, somebody may check my code
>>> and even refuse it if it is not up to the standards). But if the  
>>> idea of
>>> a full XA compatible RA is not wanted by the core team, it is not  
>>> worth
>>> the time to code it ...
>>> bye,
>>>   Roland
>> Hi Roland,
>> would love to get the contribution!
>> cheers,
>> Rob
> Anything new on this topic?
> I'm having transaction recovery problem in my production environment and
> it's getting bad.
> I've tried making the RA adapter XA compatible but most of the Managed and
> proxy object don't fit very well with the XA versions of Connection,
> XASession and such. And lack the knowledge of the inner working of ActiveMQ
> to do this in a reasonable time.
> -- 
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

View raw message