[
https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452573#comment-15452573
]
Gary Gregory commented on LOG4J2-1548:
--------------------------------------
Yes, change is risk and lots of changes compound the risk.
>From my POV, we are headed to 2.7 quick as Ralph mentioned. Anything beyond
>that like a 2.6.3 release with a single change is up to a volunteer release
>manager to step up and do. Since we are _all_ volunteers here with limited
>time, it is unlikely to happen. Our release process is not lightweight. This
>is where we can wander into the grey area consulting services, which means
>paid development. I'm not sure how that works at Apache WRT ethics, the Apache
>Way, CoC, and I'm not sure what else. Personally, I'd rather go play tag with
>my son unless I can make an extra buck to buy him a surfboard :-)
Gary
> [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]
