You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openjpa.apache.org by mi...@apache.org on 2009/12/10 19:45:23 UTC
svn commit: r889361 -
/openjpa/branches/1.0.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
Author: mikedd
Date: Thu Dec 10 18:45:22 2009
New Revision: 889361
URL: http://svn.apache.org/viewvc?rev=889361&view=rev
Log:
Doc update for connectionRetainMode always
Modified:
openjpa/branches/1.0.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
Modified: openjpa/branches/1.0.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
URL: http://svn.apache.org/viewvc/openjpa/branches/1.0.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml?rev=889361&r1=889360&r2=889361&view=diff
==============================================================================
--- openjpa/branches/1.0.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml (original)
+++ openjpa/branches/1.0.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml Thu Dec 10 18:45:22 2009
@@ -2889,7 +2889,13 @@
<para>
<literal>always</literal>: Each <classname>EntityManager</classname> obtains a
single connection and uses it until the <classname>EntityManager</classname>
-closes.
+closes. Great care should be taken when using this property if the application
+cannot close the EntityManager (ie container-managed EntityManagers in a JEE
+Application Server). In this case the connection will remain open for an
+undefined time and the application may not be able to recover from a terminated
+connection(ie if a TCP/IP timeout severs the connection to the database).
+For this reason the <literal>always</literal> option should not be used with
+container managed EntityManagers.
</para>
</listitem>
<listitem>