Pierrick HYMBERT created LOG4J2-1548:
----------------------------------------
Summary: [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
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]
