Class-New opened a new issue, #3621:
URL: https://github.com/apache/logging-log4j2/issues/3621
@ppkarwasz
` <Routing name="Routing">
<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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
