belated but I think 5.4 will help, or a current snapshot, details in https://issues.apache.org/activemq/browse/AMQ-2670
On 18 December 2009 16:28, jp.belanger <jp.belan...@gmail.com> wrote: > > From what I can see from my use, is the fact that the XARessource not being > Serializable, the Recovery engine of JBoss fails reacquire the context for > Transaction recovery. > > I tried using a custom Transaction recovery based on the JBossMQ one. > (MessagingXAResourceWrapper and MessagingXAResourceRecovery) > > But the RA doesn't return a XAConnectionFactory. So I kinda get stuck > there. > > > > Andreas Gies wrote: > > > > 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 ? > > > > > > -- > View this message in context: > http://old.nabble.com/XAResourceRecovery-for-ActiveMQ-on-JBoss-tp24933498p26845042.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
