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

Steven McCoy commented on LOG4J2-573:
-------------------------------------

A misunderstanding of the documentation I believe as the interval parameter is 
not clear:
{quote}
How often a rollover should occur based on the most specific time unit in the 
date pattern.
{quote}
In my vocabulary "_most specific time unit_" has limited meaning, is it 
supposed to imply the smallest time unit?

The enhancement request would then be about disassociating the time trigger 
with the file pattern.  For example can the logs be rolled every 6 hours but 
the files be named {{my.1.log}}, {{my.2.log}}, etc.

> TimeBasedTriggeringPolicy does not accept %i increment FilePattern
> ------------------------------------------------------------------
>
>                 Key: LOG4J2-573
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-573
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 2.0-rc1
>            Reporter: Steven McCoy
>            Priority: Minor
>
> The following configuration should be valid but raises an exception because 
> the filePattern contains no date however it does contain an increment pattern.
> {code:xml}
>     <RollingRandomAccessFile name="File" fileName="${filename}"
>         filePattern="logs/icap.log-%i">
>       <PatternLayout pattern="%m%n"/>
>       <Policies>
>         <OnStartupTriggeringPolicy />
>         <TimeBasedTriggeringPolicy interval="12" modulate="true"/>
>         <SizeBasedTriggeringPolicy size="500 MB"/>
>       </Policies>
>       <DefaultRolloverStrategy fileIndex="min" max="3"/>
>     </RollingRandomAccessFile>
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to