[logback-dev] [JIRA] Commented: (LBCORE-147) RollingPolicy MaxHistory not deleting old files
Greg Thomas (JIRA)
noreply-jira at qos.ch
Fri Sep 2 10:01:16 CEST 2011
[ http://jira.qos.ch/browse/LBCORE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12109#action_12109 ]
Greg Thomas commented on LBCORE-147:
I'm still worried about relying on the application to log frequently; Unless I've missed something ...
a) It means two different file deletion mechanisms to maintain within LBCORE; one at startup, one at rollover time.
b) The application will have to parse the logging configuration, and determine the current logging level and frequency to determine if a new log entry has of sufficient level has occurred sufficiently recently, and then create a "please ignore this" log entry at a high enough level to trigger a new rollover.
c) Any application checking for log entries to alarm will need to be altered to ignore the "please ignore this" log entry.
> 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">
> <RollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
> <layout class="ch.qos.logback.classic.PatternLayout">
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