How to manage TransactionalDriver connection in a DataSource

[sewatech]

Hi,

I'm trying to use the TransactionalDriver with a Tomcat JDBC DataSource. My problem is that sometimes, the next exception occurs :

java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction.

This exception is probably due to the fact that the close method is not called on the ConnectionImple object when it is managed in the DataSource.

My question is : how can I have a connection pool with the TransactionalDriver ?

[gytis]

It's using pooling by default. This error is thrown from the already created connection. This checking is done in most of the methods defined in java.sql.Connection interface.

Any chance you have a small reproducer for this problem?

[sewatech]

I'va added a simple example in my bitbucket repo.

It's working with a Postgres database. I have a postgres XADataSource and a Tomcat JDCB DataSource manages the Narayana JDBC connections.

The main method launches the execute method in a thread pool

Sometimes, the execute method fails with the SQLException (ARJUNA017003). The number of exception depends upon the size of the threadpool.

[tomjenkinson]

The code expects the driver to be able to do the pooling actually. We could look to making the code support a pooled wrapper. There is IronJacamar though which we could also use for this: quickstart/jca-and-hibernate at master · jbosstm/quickstart · GitHub quickstart/jca-and-tomcat at master · jbosstm/quickstart · GitHub