VijayaKumar Guddeti created LOG4J2-1242:
-------------------------------------------
Summary: Rollover fails to happen over midnight of everyday when
'date pattern' having mm or ss or SSS as the finest granularity, but working as
expected when it is dd or HH.
Key: LOG4J2-1242
URL: https://issues.apache.org/jira/browse/LOG4J2-1242
Project: Log4j 2
Issue Type: Bug
Components: Appenders
Affects Versions: 2.0-rc1
Environment: Windows and Linux
Reporter: VijayaKumar Guddeti
Rollover fails to happen over midnight of everyday when 'date pattern' having
mm or ss or SSS as the finest granularity, but working as expected when it is
dd or HH. It means log4j2 (TimeBasedTiggeringPolicy) 'modulate' property is not
functioning properly with mm or ss or SSS as most specific in 'date pattern'.
Tested with below scenarios, roll over did NOT had at midnight:
1. RollingFile - filePattern="/app/rolledoverlogs/%d{yyyy-MM-dd.HHmm}"
TimeBasedTriggeringPolicy - interval = 1440, modulate = true
2. RollingFile - filePattern="/app/rolledoverlogs/%d{yyyy-MM-dd.HHmmss}"
TimeBasedTriggeringPolicy - interval = 86400, modulate = true
3. RollingFile - filePattern="/app/rolledoverlogs/%d{yyyy-MM-dd.HHmmss.SSS}"
TimeBasedTriggeringPolicy - interval = 86400000, modulate = true
Tested with below scenarios, roll over is happening at midnight:
1. RollingFile - filePattern="/app/rolledoverlogs/%d{yyyy-MM-dd.HH}"
TimeBasedTriggeringPolicy - interval = 24, modulate = true
2. RollingFile - filePattern="/app/rolledoverlogs/%d{yyyy-MM-dd}"
TimeBasedTriggeringPolicy - interval = 1, modulate = true
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
