[logback-dev] [JIRA] Commented: (LBCORE-147) RollingPolicy MaxHistory not deleting old files

Greg Thomas (JIRA) noreply-jira at qos.ch
Thu Aug 25 22:26:16 CEST 2011

    [ http://jira.qos.ch/browse/LBCORE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12095#action_12095 ] 

Greg Thomas commented on LBCORE-147:

1. "Logback assumes that at least one LoggingEvent is generated per rollover period"

That assumption does not hold for my application; it's a web application that is running 24/7. The web server may get restarted at very infrequent intervals (perhaps a few times a year, after much form filling), but the application is typically not used at the weekend - so for two days a week the application is running but there is no logging activity. I can't believe that's an especially unusual scenario. For example, an application running 24/7 may be highly used during the working day, necessitating a hourly rollover, but idle outside of the core hours. On the bright side, in this scenario at least logback can determine maxQ.

2. "the value of Q is independent of the length of the rollover period". 

It is, but I'd suggest that the value of maxQ, i.e. the max expected idle period, is a function of the rate of logging - which is often a function of the rate of rollover. Just trying to avoid the 1440 file scenario you highlighted.

> RollingPolicy MaxHistory not deleting old files
> -----------------------------------------------
>                 Key: LBCORE-147
>                 URL: http://jira.qos.ch/browse/LBCORE-147
>             Project: logback-core
>          Issue Type: Bug
>          Components: Rolling
>    Affects Versions: 0.9.18
>         Environment: linux 2.6.18 64bits apache-tomcat-6.0.20 java/jre1.6.0_18
>            Reporter: Rafael Diaz Maurin
>            Assignee: Ceki Gulcu
>         Attachments: TimeBasedRollingWithArchiveRemovalTest.java
> The MaxHistory does not do the trick : the old files are not deleted at all :
> cat logging.xml
>  <appender name="IDP_ACCESS" class="ch.qos.logback.core.rolling.RollingFileAppender">
>         <File>/shibboleth-idp/logs/idp-access.log</File>
>             <Append>false</Append>
> 	<ImmediateFlush>true</ImmediateFlush>
>        <RollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
>             <FileNamePattern>/shibboleth-idp/logs/old/idp-access-%d{yyyy-MM-dd_HH-mm}.log.gz</FileNamePattern>
> 	    <MaxHistory>3</MaxHistory>
>         </RollingPolicy>
>         <layout class="ch.qos.logback.classic.PatternLayout">
>             <Pattern>%msg%n</Pattern>
>         </layout>
>     </appender>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the logback-dev mailing list