JDBC default connection release mode does not match documentation
Description
The documentation for 4.3 and some time earlier specifies that the default connection-release mode for JdbcTransactionFactory is AFTER_TRANSACTION, which provides a reasonable balance in an environment with high contention. However, the actual implementation class quite clearly returns ON_CLOSE.
As the configuration system was overhauled in 5, I have not been able to figure out the configuration flow there yet.
Activity
Show:
Former userOctober 5, 2018 at 8:46 PM
Versions prior to 5.3 are not under active development any more so there are no plans to change those versions.
In 5.3, hibernate.connection.acquisition_mode and hibernate.connection.release_mode are deprecated; hibernate.connection.handling_mode should be used instead.
It appears that hibernate.connection.handling_mode has not been documented in the 5.3 user guide.
Here is my understanding from looking at the code:
default for a provided connection is to acquire the connection immediately when a session is open, and hold the connection until the session is closed;
default for a non-provided JDBC resource local is it to acquire the connection when needed, and release after transaction;
default for JTA is to acquire the connection when needed, and release after statement.
, please confirm this and update the user manual with this information.
Guillaume SmetOctober 5, 2018 at 9:04 AM
can you see if we have to plan any action on this?
The documentation for 4.3 and some time earlier specifies that the default connection-release mode for
JdbcTransactionFactoryisAFTER_TRANSACTION, which provides a reasonable balance in an environment with high contention. However, the actual implementation class quite clearly returnsON_CLOSE.As the configuration system was overhauled in 5, I have not been able to figure out the configuration flow there yet.