I have a very simple app which does this :
open an xa tx
insert into db
enqueue in mule (with activemq underneath)
update db that i successfuly enqueued
close the xa tx
What i observe from the logs is :
first db update goes thro fine
enqueue also goes thro fine (of course it doesn't reflect in the ActiveMQ
web UI)
second db update also goes thro fine
but ..... just before the function returns (kicking off spring's tx close
part) I get this :
[org.mule.impl.DefaultExceptionStrategy]- Caught exception in Exception
Strategy: Session's XAResource has not been enlisted in a distributed
transaction.
javax.jms.JMSException: Session's XAResource has not been enlisted in a
distributed transaction.
at
org.apache.activemq.ActiveMQXASession.doStartTransaction(ActiveMQXASession.java:109)
Unsure why this is happening when the xa tx actually has committed the DB
tx. If the exception occured should'nt the Db tx rollback ? Probably not
because MuleClient caches the msg which goes thro fine and another thread
(the MuleDispatcher thread ?) actually picks this up and this is causing the
exception ???
Either way not sure why my config is not working. I have attached my app
context file. Would appreciate if anyone could provide some pointers. Also I
have configured my Spring’s Hibernate sessionFactory to support an XA tx.
Hopefully this is correct ???
http://www.nabble.com/file/p19111212/application-context.xml
application-context.xml
http://www.nabble.com/file/p19111212/messaging-util-applicationContext.xml
messaging-util-applicationContext.xml
-Vivek
--
View this message in context:
http://www.nabble.com/XA-Transaction-with-Spring%2C-Mule%2BActiveMQ%2C-Hibernate%2BMySql-and-Atomikos-tp19111212p19111212.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
