[jira] [Comment Edited] (LOG4J2-1242) 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.

["VijayaKumar Guddeti (JIRA)" <ji...@apache.org>]

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

VijayaKumar Guddeti edited comment on LOG4J2-1242 at 1/6/16 5:30 PM:
---------------------------------------------------------------------

Sharing below the appender which we used in the project, using this appender the Rollover at everyday midnight is NOT occurred. Please notice the finest granularity here in the date pattern is SSS, also the rollover at midnight is NOT happening when finest granularity is mm or ss. 

<RollingFile name="DNSTimingReportAppender" fileName="./logs/TestReport.csv" filePattern="./logs/DNSTimingReport-%d{yyyy-MM-dd-HHmmssSSS}.csv"
append="true" bufferedIO="fase" />
	<Policies>
		<TimeBasedTriggeringPolicy interval="86400000" modulate="true"  />
		<SizaasedTriggeringPolicy size="60 MB" />
	</Policies>
</RollingFile>

But successful rollover at midnight when date pattern having finest granularity as dd or HH. Could you share your thoughts please


was (Author: vijayakumar.guddeti):
Sharing below the appender which we used in the project, using this appender the Rollover at everyday midnight is NOT occurred. Please notice the finest granularity here in the date pattern is SSS, also the rollover at midnight is NOT happening when finest granularity is mm or ss. 

But successful rollover at midnight when date pattern having finest granularity as dd or HH

<RollingFile name="DNSTimingReportAppender" fileName="./logs/TestReport.csv" filePattern="./logs/DNSTimingReport-%d{yyyy-MM-dd-HHmmssSSS}.csv"
append="true" bufferedIO="fase" />
	<Policies>
		<TimeBasedTriggeringPolicy interval="86400000" modulate="true"  />
		<SizaasedTriggeringPolicy size="60 MB" />
	</Policies>
</RollingFile>


could you please share your thoughts.

> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org