[ 
https://issues.apache.org/jira/browse/QPID-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790227#action_12790227
 ] 

Martin Ritchie commented on QPID-2155:
--------------------------------------

The Default RollingStyle is COMPOSITE(3) which means when the file will roll 
over when it hits a certain size or based on the date specified in the 
DatePattern. 

On rollover if the destination file exists it is deleted to make way for the 
new file.  This is unlikely in a production system to affect anyone however if 
a lot of logging is being generated and the file size is small AND the 
DatePattern is set just right (currently it is set to a new file every minute) 
then it is possible to lose log data. 

WORK AROUND add param RollingStyle with value 1 which sets the logging to by 
SIZE so the DatePattern can be set to include a second value which will more 
reliably ensure we do not lose data. It will still be possible to lose some 
data if we fill our max file size within the last second. If that much logging 
is being generated then either a) we need to investigate why as the broker will 
behave very poorly b) increase max file size until we have it large enough to 
hold more than 1 second of log data c) add nanoseconds to the log file name.

FIX: a .n value should be appended to the file so that we can have log files 
with DatePattern 'YYYY' resulting in log files 2009.0, 2009.1, 2009.2, ...

> 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:[email protected]

Reply via email to