Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Thu, 9 Jan 2014 15:58:54 +0000 (UTC)
From: "Matt Sicker (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12669607.1379657534874.69049.1389283134374@arcas>
In-Reply-To: <JIRA.12669607.1379657534874@arcas>
References: <JIRA.12669607.1379657534874@arcas>
Subject: [jira] [Commented] (LOG4J2-407) JDBCAppender cannot recover from
 loss of database connectivity
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LOG4J2-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866734#comment-13866734 ] 

Matt Sicker commented on LOG4J2-407:
------------------------------------

The problem with that is there's a contract on the AbstractDatabaseAppender that writeInternal() won't call connect() more than once. Then again, this isn't using the super.connect() method, so that might be a better idea.

> 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.5#6160)

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