[
https://issues.apache.org/jira/browse/QPID-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790222#action_12790222
]
Martin Ritchie commented on QPID-2155:
--------------------------------------
Async compression will result in a call to logFile.delete() when compression
has finished.
This delete works on file name not filehandle. So if we are running with
StaticName and async compression the new qpid.log file could be deleted when
the log rolls over. This will result in all logging stopping. WORK AROUND:
disable compression or async option.
> QpidRollingFileAppender has no tests and does not appear to work.
> -----------------------------------------------------------------
>
> Key: QPID-2155
> URL: https://issues.apache.org/jira/browse/QPID-2155
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.5
> Reporter: Martin Ritchie
>
> When investigating QPID-2085 the following issues were found:
> 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.
--
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:dev-subscr...@qpid.apache.org
