From 2baa87b0407823c3ea266b78a97adc8cab068fc4 Mon Sep 17 00:00:00 2001 From: Michael Dick Date: Thu, 10 Dec 2009 18:45:16 +0000 Subject: [PATCH] Doc update for connectionRetainMode always git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@889360 13f79535-47bb-0310-9956-ffa450edef68 --- openjpa-project/src/doc/manual/ref_guide_dbsetup.xml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml b/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml index 495f0c74c..45dfb0697 100644 --- a/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml +++ b/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml @@ -3786,7 +3786,13 @@ property accepts the following values: always: Each EntityManager obtains a single connection and uses it until the EntityManager -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 always option should not be used with +container managed EntityManagers.