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

caveat to aggressive connection closing 

git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@6511 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Gavin King 2005-04-25 22:59:25 +00:00
parent 2f937fd686
commit 208e30e25c
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -512,6 +512,17 @@ Session sess = factory.getCurrentSession();
descriptors of your session bean. The lifecycle of the session is completely managed by
Hibernate.
</para>
<para>
There is one caveat to the use of <literal>auto_close_session</literal>. Due to a limitation
of the JTA spec, it is not possible for Hibernate to automatically clean up any unclosed
<literal>ScrollableResults</literal> or <literal>Iterator</literal> instances returned by
<literal>scroll()</literal> or <literal>iterate()</literal>. You <emphasis>must</emphasis>
release the underlying database cursor by calling <literal>ScrollableResults.close()</literal>
or <literal>Hibernate.close(Iterator)</literal> explicity from a <literal>finally</literal>
block. (Of course, most applications can easily avoid using <literal>scroll()</literal> or
<literal>iterate()</literal> at all from the CMT code.)
</para>
</sect2>