You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/02 06:45:00 UTC

[jira] [Commented] (LOG4J2-2542) Cron and Size Triggering Policies not rolling properly

    [ https://issues.apache.org/jira/browse/LOG4J2-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758900#comment-16758900 ] 

ASF subversion and git services commented on LOG4J2-2542:
---------------------------------------------------------

Commit 42fe68e4394c6fe335f15f9b7320aed83cc0142d in logging-log4j2's branch refs/heads/release-2.x from Ralph Goers
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=42fe68e ]

LOG4J2-2542 - CronTriggeringPolicy was not rolling properly, especially when used with the SizeBasedTriggeringPolicy


> Cron and Size Triggering Policies not rolling properly
> ------------------------------------------------------
>
>                 Key: LOG4J2-2542
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2542
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.11.1
>            Reporter: Ralph Goers
>            Priority: Major
>             Fix For: 2.11.2
>
>
> When the Cron and SizeBased Triggering policies are used together they do not roll properly. When a size-based rollover occurs that starts just before the rollover time and ends just after the file name will use the next period's timestamp but increment the index to the next number when it should have a value of 1.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)