|Modifier and Type||Method and Description|
Release a connection from Hibernate use.
Obtains a connection for Hibernate use according to the underlying strategy of this provider.
Does this connection provider support aggressive release of JDBC connections and re-acquisition of those connections (if need be) later? This is used in conjunction with
java.sql.Connection getConnection() throws java.sql.SQLException
java.sql.SQLException- Indicates a problem opening a connection
HibernateException- Indicates a problem otherwise obtaining a connection.
void closeConnection(java.sql.Connection conn) throws java.sql.SQLException
conn- The JDBC connection to release
java.sql.SQLException- Indicates a problem closing the connection
HibernateException- Indicates a problem otherwise releasing a connection.
AvailableSettings.RELEASE_CONNECTIONSto aggressively release JDBC connections. However, the configured ConnectionProvider must support re-acquisition of the same underlying connection for that semantic to work. Typically, this is only true in managed environments where a container tracks connections by transaction or thread. Note that JTA semantic depends on the fact that the underlying connection provider does support aggressive release.
trueif aggressive releasing is supported;
Copyright © 2001-2018 Red Hat, Inc. All Rights Reserved.