qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (QPID-2054) make the default Log4J configuration use a rolling file appender
Date Wed, 29 Feb 2012 10:27:59 GMT

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

Robbie Gemmell closed QPID-2054.

    Resolution: Won't Fix

We wont do this directly just now, but may include it in future logging work (e.g. moving
to SLF4J and a better supported logging implementation with a suitable rolling appender we
can use), in which case it wont need its own JIRA, closing.
> make the default Log4J configuration use a rolling file appender
> ----------------------------------------------------------------
>                 Key: QPID-2054
>                 URL: https://issues.apache.org/jira/browse/QPID-2054
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: M2.1, M3, M4, 0.5, 0.6
>            Reporter: Robbie Gemmell
> The current default Log4J configuration does not use a rolling file appender. As a result,
when the Log4J configuration is reloaded the existing file is cleared as the new configuration
takes effect. Thus, if the XML WatchDog is active, or the management console s used to manually
reload the Log4J configuration the existing log file contents will be lost.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message