doc release_mode

git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@6680 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Gavin King 2005-05-04 00:30:31 +00:00
parent fb35c15f67
commit 13f00214e4
1 changed files with 13 additions and 8 deletions

View File

@ -669,17 +669,22 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]></programlisting>
</row> </row>
<row> <row>
<entry> <entry>
<literal>hibernate.connection.aggressive_release</literal> <literal>hibernate.connection.release_mode</literal>
</entry> </entry>
<entry> <entry>
Enables Hibernate to aggressively release JDBC Connections, if supported Specify when Hibernate should release JDBC connections. By default,
supported by the <literal>ConnectionProvider</literal>. By default a JDBC a JDBC connection is held until the session is explicitly closed or
connection is held for the lifespan (excluding disconnected state) of the Session; disconnected. For an application server JTA datasource, you should use
this does not play well inside managed environments implementing connection <literal>after_statement</literal>, to aggressively release connections
"containment" checks. Recommended in managed environments. 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
<literal>after_transaction</literal>. <literal>auto</literal> will
choose <literal>after_statement</literal> for the JTA and CMT transaction
strategies and <literal>after_transaction</literal> for the JDBC
transaction strategy.
<para> <para>
<emphasis role="strong">eg.</emphasis> <literal>on_close</literal> | <literal>after_transaction</literal> |
<literal>true</literal> | <literal>false</literal> <literal>after_statement</literal> | <literal>auto</literal>
</para> </para>
</entry> </entry>
</row> </row>