Hi.

I'm using Hibernate v 2.1.6.

I use a custom jdbc connection provider.
Everything works nice with it except one :

When an error occur on a query made by Hibernate, the connection is not returned to the pool.
My pool is instructed to create at most xx connections so, after xx Hibernate SQLException, the application is down.

I suppose it runs as designed to stop using a potential dirty connection, but my pool already do that and I'm not sure it is hibernate's job to do it.

Also, even in this case, I don't understand why the connection is not, at least, closed ? (therefore, I saw that all PreparedStatement created are correctly closed).

Maybe there is an option or a way to wrap around ?

Thanks in advance for any help.

Mike

In addition to the getConnection() method, the ConnectionProvider interface also defines the closeConnection() method. Its up to the implementation (i.e., your code) to do whatever needs to get done when Hibernate says its done with the connection.

Ok, I understand this and my closeConnection() returns the connection to the pool.
But the problem is that when an SQL error occur, closeConnection() is not called !!!

Mike