activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Guggi <>
Subject XA Transaction with multiple xa-connections not working on rollback
Date Sat, 06 Apr 2013 18:46:45 GMT

we use spring's DMLC using an xa-pooledconnectionfactory

when the DMLC receives a message the (test) message-lister just sends a
message to another queue using spring's jmstemplate. this jms-template also
uses a xa-pooledconnectionfactory (but another instance)

that meas that we have two activemq xa-connections - one by the listener
and the other by the jms-template

if the message-listener throws a runtime-exception after jmstemplate send,
the rollback is not properly performed.

i can see that org.apache.activemq.TransactionContext.end(xid,flags) is
only called once for the dmlc-connection - so therefore no rollback is not
performed for the other xa-connection/session, which leads to a (jta)
system-exception on the next-message, because the pooldcf returns the
cached session

any ideas how this could happen - this might be a jta issue? btw. we are
using glassfish-

thank you,

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message