You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by gg...@apache.org on 2022/02/06 13:23:38 UTC

[logging-log4j2] branch release-2.x updated: [LOG4J2-2715] JDBCAppender commits to the DB a JTA RollbackOnly transaction and causes DB inconsistency.

This is an automated email from the ASF dual-hosted git repository.

ggregory pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


The following commit(s) were added to refs/heads/release-2.x by this push:
     new 910f581  [LOG4J2-2715] JDBCAppender commits to the DB a JTA RollbackOnly transaction and causes DB inconsistency.
910f581 is described below

commit 910f5812c836aa0afeb4ffde1c9da9f8c3e878a3
Author: Gary Gregory <ga...@gmail.com>
AuthorDate: Sun Feb 6 08:23:31 2022 -0500

    [LOG4J2-2715]
    JDBCAppender commits to the DB a JTA RollbackOnly transaction and causes
    DB inconsistency.
    
    Update documentation.
---
 src/site/xdoc/manual/appenders.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/site/xdoc/manual/appenders.xml b/src/site/xdoc/manual/appenders.xml
index 12b3fc0..0e98d14 100644
--- a/src/site/xdoc/manual/appenders.xml
+++ b/src/site/xdoc/manual/appenders.xml
@@ -1103,10 +1103,10 @@ CREATE TABLE logs (
           <p>When configuring the JDBCAppender, you must specify a <code>ConnectionSource</code> implementation from
             which the Appender gets JDBC connections. You must use exactly one of the following nested elements:</p>
           <ul>
-            <li><a href="#JDBCDataSource"><code>&lt;DataSource&gt;</code></a>: Uses JNDI.</li>
+            <li><a href="#JDBCDataSource"><code>&lt;DataSource&gt;</code></a>: Uses JNDI. Do not share this connection with other clients.</li>
             <li><a href="#JDBCConnectionFactory"><code>&lt;ConnectionFactory&gt;</code></a>: Points to a class-method pair to provide JDBC connections.</li>
             <li><a href="#JDBCDriverManager"><code>&lt;DriverManager&gt;</code></a>: A quick and dirty way to get off the ground, no connection pooling.</li>
-            <li><a href="#JDBCPoolingDriver"><code>&lt;PoolingDriver&gt;</code></a>: Uses Apache Commons DBCP to provide connection pooling.</li>
+            <li><a href="#JDBCPoolingDriver"><code>&lt;PoolingDriver&gt;</code></a>: Uses <a href="https://commons.apache.org/proper/commons-dbcp/">Apache Commons DBCP</a> to provide connection pooling.</li>
           </ul>
           <a name="JDBCDataSource"/>
           <table>