I would start with a simple use case and verify from trace level
logging that everything is as expected with respect to transaction
demarcation and connection pooling.
But note, that the RA should do its own pooling and transaction
management as the contracts between j2e and a resource manager (RA
I suspect that, because I am using a connection pool with the RA adapter,
somewhere somehow the transaction information is not cleared when the
connection is returned to the pool. In another post earlier, I had another
error:
Caused by: javax.jms.JMSException: The resource is allready being used in
we would need some more context, but that exception indicates that the
transaction associated with that session has already completed.
Trace level logging on both activemq and jboss may help diagnose
exactly what is going on.
And ideally, if you could provide a test case that can demonstrate the
p
