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 (RAR) cover all that stuff. On 27 May 2011 14:34, lexsoto <lexs...@gmail.com> wrote: > 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 > transaction context. > at > org.apache.activemq.ra.ManagedTransactionContext.setUseSharedTxContext(ManagedTransactionContext.java:47 > which is not exactly the same, but it seems related. > > I will do more testing reducing the number of connections in the pool. > I am really looking for pointers, and hints that help me investigate. > > Does it sound I am in the right path? > > Thanks > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Transaction-issues-tp3549910p3555346.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://fusesource.com http://blog.garytully.com
