[logback-dev] [JIRA] Commented: (LBCLASSIC-105) File not rolling over with SizeBasedTriggeringPolicy

Ceki Gulcu (JIRA) noreply-jira at qos.ch
Fri Jan 16 11:29:29 CET 2009

    [ http://jira.qos.ch/browse/LBCLASSIC-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11008#action_11008 ] 

Ceki Gulcu commented on LBCLASSIC-105:

Looking at the configuration file, the File property reads "${catalina.home}/logs/rp.log" while the FileNamePattern property is set to "rp.%i.log.gz". This means that the archived files will be located in current folder. If you wish to have the archived files located next to the current log file, you need to set FileNamePattern property to "${catalina.home}/logs/rp.%i.log.gz"

I have tested the configuration file provided by Gianni. It seems to work just fine.

If there are indeed problems with the roll over, they should be visible by printing logback's internal status. Here is code that does that:

    LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory();

It should be invoked after roll over occurs.

> File not rolling over with SizeBasedTriggeringPolicy
> ----------------------------------------------------
>                 Key: LBCLASSIC-105
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-105
>             Project: logback-classic
>          Issue Type: Bug
>    Affects Versions: 0.9.14
>            Reporter: Ceki Gulcu
>            Assignee: Ceki Gulcu
> Original report http://qos.ch/pipermail/logback-user/2009-January/000878.html

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