[
https://issues.apache.org/jira/browse/QPID-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765014#action_12765014
]
Martin Ritchie commented on QPID-2085:
--------------------------------------
On further testing the QpidRollingFileAppender does not appear to behave as
expected from the configuration.
Have noticed the following:
- qpid.log being archived shortly after creation, resulting in no log file for
the broker. (When using StaticName)
- Log files being archived before 10MB setting, using default configuration.
- Log files index not being used as described in the comments. file .0 is
always the current head of the log rather than 'n' as described.
If we want to keep logs from previous broker runs then we should re-investigate
if the stock log4j RollingFileApender will address our current needs.
> Broker Log4j configuration causes the specified log4j to be cleared on startup
> ------------------------------------------------------------------------------
>
> Key: QPID-2085
> URL: https://issues.apache.org/jira/browse/QPID-2085
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: 0.6
>
>
> Set the default log4j.xml file for the broker to append to the existing log
> file rather than overwritting it.
> Provide an easy mechanism to change the default rather than editing the log4j
> file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
