From e1fa1647fb1e08e5f0f41273be99fc77592b3af6 Mon Sep 17 00:00:00 2001
From: Vlad Mihalcea <mih_vlad@yahoo.com>
Date: Wed, 23 Mar 2016 09:12:47 +0200
Subject: [PATCH] HHH-7412 - JDBCTransactionFactory.getDefaultReleaseMode()
 returns incorrect ConnectionReleaseMode

Document that JDBC transactions use ON_CLOSE connection release mode
---
 .../src/main/docbook/manual/en-US/content/transactions.xml      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/src/main/docbook/manual/en-US/content/transactions.xml b/documentation/src/main/docbook/manual/en-US/content/transactions.xml
index c059115493..5bbee6b050 100644
--- a/documentation/src/main/docbook/manual/en-US/content/transactions.xml
+++ b/documentation/src/main/docbook/manual/en-US/content/transactions.xml
@@ -1090,7 +1090,7 @@ session.close();]]></programlisting>
                     <literal>auto</literal> (the default): this choice delegates to the release mode
                     returned by the <literal>org.hibernate.transaction.TransactionFactory.getDefaultReleaseMode()</literal>
                     method.  For JTATransactionFactory, this returns ConnectionReleaseMode.AFTER_STATEMENT; for
-                    JDBCTransactionFactory, this returns ConnectionReleaseMode.AFTER_TRANSACTION.  Do not
+                    JDBCTransactionFactory, this returns ConnectionReleaseMode.ON_CLOSE.  Do not
                     change this default behavior as failures due to the value of this setting
                     tend to indicate bugs and/or invalid assumptions in user code.
                 </para>