[jira] [Created] (LOG4J2-407) JDBCAppender cannot recover from loss of database connectivity

["Michael Kloster (JIRA)" <ji...@apache.org>]

Michael Kloster created LOG4J2-407:
--------------------------------------

             Summary: 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


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org