logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Brouwer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-609) StatusConfiguration doesn't close files
Date Thu, 01 May 2014 01:41:24 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Bruce Brouwer updated LOG4J2-609:

    Attachment: log4j2-609.patch

With log4j2-609.patch, now all tests pass with a clean install on Windows. This patch gets
into some of the deeper guts of log4j that I haven't had to deal with before, so I would appreciate
someone vetting what I did. 

But at least all the tests pass, so that's good. 

> StatusConfiguration doesn't close files
> ---------------------------------------
>                 Key: LOG4J2-609
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-609
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0-rc1
>            Reporter: Bruce Brouwer
>         Attachments: log4j2-609.patch
> {{org.apache.logging.log4j.core.config.status.StatusConfiguration}} allows you to specify
a destination such as "out", "err" or a file name. If specifying a file, that file stream
is used when creating a {{StatusConsoleListener}} that is added to the {{StatusLogger}}. Those
{{StatusLogger}} listeners are never cleaned up when, for example, the {{XmlConfiguration}}
is reconfigured or when the {{LoggerContext}} is shut down (e.g. in {{InitialLoggerContext.apply()}}).
This leaves open file handles and is the source of the failing test {{FileOutputTest}} on

This message was sent by Atlassian JIRA

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

View raw message