[LOG4J2-407] JDBCAppender cannot recover from loss of database connectivity

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta9
• Fix Version/s: 2.0-rc1
• Component/s: Appenders
• Assignee: Nick Williams
• Reporter: Michael Kloster
• Created: 20/Sep/13 06:12
• Updated: 12/May/14 06:20
• Resolved: 08/Feb/14 02:56

Description

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.

Issue Links

• is related to: LOG4J2-442 Log4j2 Database insert problem in Websphere
• is related to: LOG4J2-457 JDBCAppender does not release JDBC connections to the connection pool when WAR/EAR is stopped
• is related to: LOG4J2-438 JDBCDatabaseManager does not send commit command
• is related to: LOG4J2-489 Should JPADatabaseManager being using so many transactions?
• relates to: LOG4J2-442 Log4j2 Database insert problem in Websphere
• relates to: LOG4J2-457 JDBCAppender does not release JDBC connections to the connection pool when WAR/EAR is stopped
• relates to: LOG4J2-469 FailoverAppender does not retry back for Primary target
• relates to: LOG4J2-438 JDBCDatabaseManager does not send commit command
• relates to: LOG4J2-489 Should JPADatabaseManager being using so many transactions?