Return-Path: 
 <log4j-dev-return-26385-apmail-logging-log4j-dev-archive=logging.apache.org@logging.apache.org>
X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org
Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id E08CF10151
	for <apmail-logging-log4j-dev-archive@www.apache.org>;
 Sat,  8 Feb 2014 00:03:27 +0000 (UTC)
Received: (qmail 33361 invoked by uid 500); 8 Feb 2014 00:03:24 -0000
Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org
Received: (qmail 33254 invoked by uid 500); 8 Feb 2014 00:03:22 -0000
Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:log4j-dev-unsubscribe@logging.apache.org>
List-Help: <mailto:log4j-dev-help@logging.apache.org>
List-Post: <mailto:log4j-dev@logging.apache.org>
List-Id: "Log4J Developers List" <log4j-dev.logging.apache.org>
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Delivered-To: mailing list log4j-dev@logging.apache.org
Received: (qmail 33222 invoked by uid 99); 8 Feb 2014 00:03:22 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Feb 2014 00:03:22 +0000
Date: Sat, 8 Feb 2014 00:03:22 +0000 (UTC)
From: "Nick Williams (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12681887.1385730727349.9093.1391817802124@arcas>
In-Reply-To: <JIRA.12681887.1385730727349@arcas>
References: <JIRA.12681887.1385730727349@arcas>
Subject: [jira] [Assigned] (LOG4J2-457) JDBCAppender does not release JDBC
 connections to the connection pool when WAR/EAR is stopped
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/LOG4J2-457?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Williams reassigned LOG4J2-457:
------------------------------------

    Assignee: Nick Williams

> JDBCAppender does not release JDBC connections to the connection pool whe=
n WAR/EAR is stopped
> -------------------------------------------------------------------------=
--------------------
>
>                 Key: LOG4J2-457
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-457
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.0-beta9
>         Environment: JBOSS application server, PostgreSQL database
>            Reporter: Tihomir Me=C5=A1=C4=8Di=C4=87
>            Assignee: Nick Williams
>
> We use log4j 2 for logging inside our J2EE app (packaged as EAR, log4j JA=
Rs 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 a=
ppender is configured to use a DataSource for fetching connections. The app=
ender is configured as follows:
>     <JDBC name=3D"jdbcAppender" tableName=3D"log_entries">
>       <DataSource jndiName=3D"java:jboss/datasources/XyzDS" />
>       <Column name=3D"log_entries_message" isUnicode=3D"false" pattern=3D=
"%message" />
>       <Column name=3D"log_entries_type" literal=3D"0" />
>       .....
> The problem is: after the EAR is stopped (undeployed) log4j is not releas=
ing the JDBC connection back to the connection pool, and after we stop/star=
t the application a couple of times, our server becomes useless because the=
re 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



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