You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Nick Williams (JIRA)" <ji...@apache.org> on 2014/02/08 03:58:19 UTC
[jira] [Resolved] (LOG4J2-407) JDBCAppender cannot recover from
loss of database connectivity
[ https://issues.apache.org/jira/browse/LOG4J2-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Williams resolved LOG4J2-407.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database appenders now connect to the database (i.e., borrow from the connection pool) and begin a transaction on every flush or every non-buffered {{writeInternal}}, then commit and disconnect (i.e., return to pool) at the end of the flush or non-buffered {{writeInternal}}.
Note also that the {{<DriverManager...>}} connection source plugin is no longer available. It was removed because it was unsafe and didn't support connection pooling. Please use the {{<DataSource...>}} or {{<ConnectionFactory...>}} connection source plugins, instead.
> JDBCAppender cannot recover from loss of database connectivity
> --------------------------------------------------------------
>
> Key: LOG4J2-407
> URL: https://issues.apache.org/jira/browse/LOG4J2-407
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.0-beta9
> Reporter: Michael Kloster
> Assignee: Nick Williams
> Fix For: 2.0-rc1
>
>
> The JDBCAppender holds a single database connection for all its logging. If that database connection is closed, it does not attempt to make a new connection.
> Many connection pools automatically close connections after a certain amount of inactivity. (This can be worked around by properly configuring a pool).
> Database connectivity issues are also common enough that a long running application may experience temporary network issues. When the network comes back online, the logging will not resume.
> I've been meaning to submit a patch for this, but I haven't gotten to it. Since I saw that you are looking to come out of beta soon, I thought I would log this issue in case someone else has time to write the patch before I get to it.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org