After upgrading to hibernate 4.2.4 from 3.6 database connections are not returned to pool after initialisation of lazy collection. As result connection pool is exhausted very quickly when number of users exceeds number of connections in the pool.
Similar symptoms are described in HHH-4808 but we haven't observed those problems in Hib. 3.1-3.6


Relevant settings:

hibernate.connection.autocommit=true
hibernate.connection.release_mode=after_transaction



After collection is initialized there is no open transaction. So according to setting connection has to be released


In hibernate 3.6 connection was released (through indirect call to ConnectionManager.aggresiveRelease() from OneToManyLoader).
This is very critical change for our usage scenario. Was this change intentional? Is it possible to activate old behaviour through some combination of settings?
Thank you.

Hi guys,

I observe the same issue. Any suggestions?