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

Steffen Offermann commented on LOG4J2-1548:
-------------------------------------------

Yes, using branches per minor version would really help. We do that at our 
company, and that's why for us releasing a patch for a minor version is just a 
matter of minutes - including the publishing of the Changelogs, etc.

Gary, as far as I understood there already was a pull request or a patch for 
this specific bug?

I don't know what you mean by "use MLs". Sorry, I'm not great at memorizing 
abbreviations. ;)


> [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely 
> after first fire
> --------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-1548
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1548
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.6.2
>            Reporter: Pierrick HYMBERT
>            Priority: Blocker
>             Fix For: 2.7
>
>         Attachments: LOG4J2-1548-testcase-2.patch, 
> LOG4J2-1548-testcase-cleanFoldersRule.patch, LOG4J2-1548-testcase.patch, 
> LOG4J2-1548.patch
>
>
> After first fire at fixed time, rename/archive action is sheduled infinitely.
> Example of configuration:
> {code:xml}
> <RollingFile name="RollingFile"
>        fileName="target/rolling-cron-once-a-day/rollingtest.log"
>        
> filePattern="target/rolling-cron-once-a-day/rollingtest-%d{yyyyMMdd}_%d{HHmmss}-%i.log.gz"
>        immediateFlush="true">
>       <PatternLayout pattern="%d %p %C{1.} [%t] %m%n" />
>       <CronTriggeringPolicy schedule="27 58 13 * * ?"/>
>     </RollingFile>
> {code}
> First trigger is scheduled at 13:58:27 then every new log entry generates an 
> archive file.
> Test case and suggested fix attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to