[LOG4J2-1548] [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.6.2
• Fix Version/s: 2.7
• Component/s: Core
• Assignee: Gary D. Gregory
• Reporter: Pierrick HYMBERT
• Created: 24/Aug/16 11:04
• Updated: 12/Sep/16 00:06
• Resolved: 24/Aug/16 15:53

Description

After first fire at fixed time, rename/archive action is sheduled infinitely.

Example of configuration:

<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>

First trigger is scheduled at 13:58:27 then every new log entry generates an archive file.

Test case and suggested fix attached.

Issue Links

• is a clone of: LOG4J2-1480 CronTriggeringPolicy timing / file deletion issue