Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

documented hibernate.connection.aggressive_release 

git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@6526 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Steve Ebersole 2005-04-26 15:53:46 +00:00
parent 76eaef099c
commit b9b77e49b8
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
reference/en/modules/configuration.xml
View File

@ -523,7 +523,7 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]></programlisting>
</tgroup>
</table>
<table frame="topbot" id="configuration-jdbc-properties" revision="7">
<table frame="topbot" id="configuration-jdbc-properties" revision="8">
<title>Hibernate JDBC and Connection Properties</title>
<tgroup cols="2">
<colspec colname="c1" colwidth="1*"/>
@ -672,11 +672,12 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]></programlisting>
<literal>hibernate.connection.aggressive_release</literal>
</entry>
<entry>
Enables Hibernate to aggressively release JDBC Connections, provided this behaviour is
Enables Hibernate to aggressively release JDBC Connections, provided this behavior 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.
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.
</entry>
</row>
<row>