From 76eaef099c741ab2a99364a53cf5b963464d2c0c Mon Sep 17 00:00:00 2001
From: Steve Ebersole <steve@hibernate.org>
Date: Tue, 26 Apr 2005 15:41:51 +0000
Subject: [PATCH] documented hibernate.connection.aggressive_release

git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@6525 1b8cb986-b30d-0410-93ca-fae66ebed9b2
---
 reference/en/modules/configuration.xml | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/reference/en/modules/configuration.xml b/reference/en/modules/configuration.xml
index 56b368b0df..ef0d32fe15 100644
--- a/reference/en/modules/configuration.xml
+++ b/reference/en/modules/configuration.xml
@@ -667,6 +667,18 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]></programlisting>
                             </para>
                         </entry>
                     </row>
+                    <row>
+                        <entry>
+                            <literal>hibernate.connection.aggressive_release</literal>
+                        </entry>
+                        <entry>
+                            Enables Hibernate to aggressively release JDBC Connections, provided this behaviour is
+                            supported by the configured <literal>ConnectionProvider</literal>.  The default Hibernate
+                            behaviour is to cache a Connection for the entire lifespan (excluding disconnect/reconnect
+                            calls) of the Session; this does not play well with certain usage scenarios inside managed
+                            environments implementing Connection "containment" checks.
+                        </entry>
+                    </row>
                     <row>
                     <entry>
                         <literal>hibernate.connection.<emphasis>&lt;propertyName&gt;</emphasis></literal>