From cc7621952a81d6d7fbe25a9255853982693e019a Mon Sep 17 00:00:00 2001 From: Christian Bauer Date: Tue, 26 Apr 2005 21:24:26 +0000 Subject: [PATCH] Minor git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@6536 1b8cb986-b30d-0410-93ca-fae66ebed9b2 --- reference/en/modules/configuration.xml | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/reference/en/modules/configuration.xml b/reference/en/modules/configuration.xml index d37d64bd57..b234915639 100644 --- a/reference/en/modules/configuration.xml +++ b/reference/en/modules/configuration.xml @@ -672,12 +672,15 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]> hibernate.connection.aggressive_release - Enables Hibernate to aggressively release JDBC Connections, provided this behavior is - supported by the configured ConnectionProvider. The default Hibernate - behavior is to cache a Connection for the entire lifespan (excluding disconnect/reconnect - calls) of the Session; this does not play well inside managed environments implementing - Connection "containment" checks. Thus, setting this to true is recommended in managed - environments. + 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. + + eg. + true | false + @@ -1414,6 +1417,12 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]> + + Depending on your environment, you might have to set the configuration option + hibernate.connection.aggressive_release to true if your + application server shows "connection containment" exceptions. + + Transaction strategy configuration