I am using Websphere 5, Hibernate 2 and DB2 7.2.

I have a connection leak when running under websphere, but not when running under Tomcat with the same codebase. Under tomcat I'm using a dbcp connection pool and a jndi datasource, so Hibernate shouldn't be doing any pooling. Under Websphere I'm using the COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource which as I understand it is not a "transacted" datasource.

Does Hibernate require a transacted datasource? I have tried using the COM.ibm.db2.jdbc.DB2XADataSource instead, but the application doesn't work right when I use that datasource.

I know Hibernate is not causing the connection leak, but I'm wondering if there are setup requirements for the connection pool that anyone knows of that might affect this?

Thanks for your help!

Jenica

The datasource given to Hibernate does not have to be XA transacted.

I finally found the cause of our connection leak in Websphere. I wanted to put a note here so that if anyone else runs into this they'll be able to fix it more quickly!!

Hibernate requires that the connection have autocommit=false, and the connection received from Websphere has autocommit = true. So, after retrieving the connection from the pool I set autocommit to false.

If I set autocommit back to true BEFORE returning the connection to the websphere pool, it works perfectly. If I don't, there's a very difficult to diagnose leak!

We're using Websphere 5, DB2 7.2 client, DB2 7.1 Database, and Hibernate 2.0.

Jenica[/list]