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 "Dimitry Declercq (JIRA)" <ji...@apache.org> on 2013/11/13 08:54:21 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13821043#comment-13821043 ]
Dimitry Declercq commented on LOG4J2-407:
-----------------------------------------
Any progress on this? I logged an issue yesterday concerning this (before I found this one) LOG4J2-449
I'm available to test any solution you have for this. We are also conducting some MySQL database tests next week (failover, network failures, ...), if you can provide me with a patched version we can check the behaviour of Log4J in these scenario's as well.
> 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
>
> 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#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org