openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mik...@apache.org
Subject svn commit: r889338 - /openjpa/branches/1.2.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
Date Thu, 10 Dec 2009 17:09:26 GMT
Author: mikedd
Date: Thu Dec 10 17:09:25 2009
New Revision: 889338

URL: http://svn.apache.org/viewvc?rev=889338&view=rev
Log:
Doc update for connectionRetainMode always

Modified:
    openjpa/branches/1.2.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml

Modified: openjpa/branches/1.2.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
URL: http://svn.apache.org/viewvc/openjpa/branches/1.2.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml?rev=889338&r1=889337&r2=889338&view=diff
==============================================================================
--- openjpa/branches/1.2.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml (original)
+++ openjpa/branches/1.2.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml Thu Dec 10
17:09:25 2009
@@ -3599,7 +3599,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>



Mime
View raw message