[LOG4J2-457] JDBCAppender does not release JDBC connections to the connection pool when WAR/EAR is stopped

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta9
• Fix Version/s: 2.0-rc1
• Component/s: Appenders

Environment

JBOSS application server, PostgreSQL database

• Assignee: Nick Williams
• Reporter: Tihomir Meščić
• Created: 29/Nov/13 13:12
• Updated: 08/Feb/14 03:01
• Resolved: 08/Feb/14 02:58

Description

We use log4j 2 for logging inside our J2EE app (packaged as EAR, log4j JARs are bundled inside). The app is deployed on JBOSS EAP 6.1 app server. We are using the JDBCAppender for logging to a PostgreSQL database, and the appender is configured to use a DataSource for fetching connections. The appender is configured as follows:

<JDBC name="jdbcAppender" tableName="log_entries">
<DataSource jndiName="java:jboss/datasources/XyzDS" />
<Column name="log_entries_message" isUnicode="false" pattern="%message" />
<Column name="log_entries_type" literal="0" />
.....

The problem is: after the EAR is stopped (undeployed) log4j is not releasing the JDBC connection back to the connection pool, and after we stop/start the application a couple of times, our server becomes useless because there are no more free connections in the connection pool. I've looked at the thread dump of the server and there are a lot of threads like this:
org.apache.logging.log4j.core.LoggerContext$ShutdownThread @ 0xbe447138

Issue Links

• is related to: LOG4J2-442 Log4j2 Database insert problem in Websphere
• is related to: LOG4J2-407 JDBCAppender cannot recover from loss of database connectivity
• 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-407 JDBCAppender cannot recover from loss of database connectivity
• relates to: LOG4J2-438 JDBCDatabaseManager does not send commit command
• relates to: LOG4J2-489 Should JPADatabaseManager being using so many transactions?