[
https://issues.apache.org/jira/browse/QPID-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reassigned QPID-2054:
------------------------------------
Assignee: (was: Robbie Gemmell)
Given that our custom rolling file appender (that we shouldnt need to maintain,
we arnet a logging project) has some issues and log4js own does too, I think I
am probably leaning toward moving away from log4j and using somthing that does
this for us before this change will occur.
> 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:[email protected]
