diff --git a/reference/en/modules/configuration.xml b/reference/en/modules/configuration.xml index b234915639..a3ce112f96 100644 --- a/reference/en/modules/configuration.xml +++ b/reference/en/modules/configuration.xml @@ -669,17 +669,22 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]> - hibernate.connection.aggressive_release + hibernate.connection.release_mode - Enables Hibernate to aggressively release JDBC Connections, if supported - supported by the ConnectionProvider. By default a JDBC - connection is held for the lifespan (excluding disconnected state) of the Session; - this does not play well inside managed environments implementing connection - "containment" checks. Recommended in managed environments. + Specify when Hibernate should release JDBC connections. By default, + a JDBC connection is held until the session is explicitly closed or + disconnected. For an application server JTA datasource, you should use + after_statement, to aggressively release connections + after every JDBC call. For a non-JTA connection, it often makes sense to + release the connection at the end of each transaction, by using + after_transaction. auto will + choose after_statement for the JTA and CMT transaction + strategies and after_transaction for the JDBC + transaction strategy. - eg. - true | false + on_close | after_transaction | + after_statement | auto