Used on Routes, CronTriggeringPolicy is not executed correctly

[Class-New]

@ppkarwasz

`

	  <Routes pattern="$${ctx:ROUTINGKEY}">
		<Route key="$${ctx:ROUTINGKEY}">
		  <RollingFile name="Rolling-default" fileName="${log.path}/common.log"
				filePattern="${log.path}/common-%d{yyyy-MM-dd}-%i.log.gz">
			<PatternLayout>
				<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %X{flowno} %t %-5p %c:%L %m%n</pattern>
			</PatternLayout>
			<Policies>
			  <SizeBasedTriggeringPolicy size="256 MB" />
			</Policies>
			<DefaultRolloverStrategy max="100"/>
		  </RollingFile>
		</Route>
		<Route>
		  <RollingFile name="Rolling-${ctx:ROUTINGKEY}" fileName="${log.path}/${ctx:ROUTINGKEY}.log"
			filePattern="${log.path}/${ctx:ROUTINGKEY}-%d{yyyy-MM-dd}-%i.log.gz">
			<PatternLayout>
				<pattern>%d{yyyy-MM-dd 'at' HH:mm:ss.SSS} %X{flowno} %t %-5p %c:%L %m%n</pattern>
			</PatternLayout>
			<Policies>
				<CronTriggeringPolicy evaluateOnStartup="true" schedule="0 0 0 * * ?">
				<SizeBasedTriggeringPolicy size="256 MB" />
			</Policies>
			<DefaultRolloverStrategy max="100"/>
		  </RollingFile>
		</Route>
	  </Routes>
	</Routing>`

I expected every time the log roll back to the specified folder, is looking forward to every day 0 am to log rolled back, but the test found that don't take effect, only the present a log time will only take effect on arrival (TimeBasedTriggeringPolicy is so, That's why I changed the CronTriggeringPolicy), and another interesting phenomenon is that schedule="0 * * * * ?" The rollback can be performed every minute. Set schedule to "0 0 * * * ?". Or schedule="0 0 0 * * ?" Can't handle it correctly

spring-boot-starter-log4j2: 2.17.8

[ppkarwasz]

Hi @Class-New,

Thanks for the report! I may have misunderstood the nature of your problem, so please correct me if I did.

Here’s a quick overview of how the two triggering policies work:

• TimeBasedTriggeringPolicy rolls over synchronously—when the first log event of the new day is written. So the rollover happens only after that first event, meaning no event from the new day will end up in the old file. It uses the timezone from your %d pattern (typically your system timezone).

• CronTriggeringPolicy rolls over asynchronously at the exact scheduled time (e.g., midnight), regardless of log activity. Due to its async nature, events close to the scheduled time might end up in either the old or new file. It uses the system’s default timezone.

Two more details that matter in your setup:

• The Routing appender creates its actual appenders lazily—only when a log event with a given ROUTINGKEY occurs. So if no event is logged for a key on a given day, its appender (and therefore the rollover logic) is never initialized, and no rollover will happen at the end of that day.

• The definition of “end of day” depends on the timezone used. Since most timezones differ from UTC by full hours, timezone mismatches are less noticeable with minute- or hourly-based schedules—but they can cause confusion with daily rollovers if the timezone isn’t configured as expected.

Could you clarify which of these behaviors isn’t working as expected, or what you believe might be a bug?