[ 
https://issues.apache.org/jira/browse/LOG4J2-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082990#comment-15082990
 ] 

VijayaKumar Guddeti commented on LOG4J2-1242:
---------------------------------------------

Not exactly related to LOG4J2 - 1232. 

The issue is, Log4j rollover has to happen based on finest granularity 
(dd/HH/mm/ss/SSS) of datePattern inputted to ‘filePattern’ property of 
RollingFile appender. But its not rolledover when finest granularity is 
mm/ss/SSS

Successful date pattern for midnight rollover are:
1.      HHmmssSSS-yyyy-MM-dd  (TimeBasedTiggeringPolicy - interval = 1 , 
modulate = true)
2.      mmssSSS-yyyy-MM-dd.HH (TimeBasedTiggeringPolicy - interval = 24 , 
modulate = true)

Unsupported date patterns for RollingFile at midnight are:
1.      yyyy-MM-dd.HHmm (TimeBasedTiggeringPolicy - interval=1440 , modulate = 
true)
2.      yyyy-MM-dd.HHmmss(TimeBasedTiggeringPolicy - interval=86400 , modulate 
= true)
3.      yyyy-MM-dd.HHmmssSSS(TimeBasedTiggeringPolicy - interval=86400000 , 
modulate = true)

I'm happy to furnish if any other info needed.


> Rollover fails to happen over midnight of everyday when RollingFile 
> appender's 'filepattern' 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
>              Labels: features
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> 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]

Reply via email to