[
https://issues.apache.org/jira/browse/LOG4J2-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091798#comment-15091798
]
Nikolai commented on LOG4J2-1232:
---------------------------------
Gregory,
{{org.apache.logging.log4j.core.appender.rolling.PatternProcessor#getNextTime}}
may be easy fixed by adding two lines:
{code}
currentCal.setMinimalDaysInFirstWeek(7);
cal.setMinimalDaysInFirstWeek(7);
{code}
Also, in your test (thanks for writing it!) expected is 3 January (due to force
1st day of the week to be Sunday).
{{00}} is octal integers :-)
> Incorrect log rotation in last week of year
> -------------------------------------------
>
> Key: LOG4J2-1232
> URL: https://issues.apache.org/jira/browse/LOG4J2-1232
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.3, 2.5
> Reporter: Nikolai
> Priority: Critical
>
> I have log4j2.xml configuration with several log-files definitions like:
> {code:xml}
> <RollingRandomAccessFile name="FIX_MESSAGES_FILE_MARKET_DATA"
> fileName="logs/market_data_msg.log"
>
> filePattern="logs/market_data_msg.log-%d{yyyy-MM-'W'W}"
> immediateFlush="false">
> <PatternLayout pattern="%m%n"/>
> <Policies>
> <TimeBasedTriggeringPolicy/>
> </Policies>
> </RollingRandomAccessFile>
> {code}
> Today (2015-12-28) all log files suddenly become almost empty. Reason in
> permanent rotation current log file in file "market_data_msg.log-2014-12-W5"
> (wrong year). As result of permanent rotation both files contains only 0 or 1
> lines and information is lost!
> Obviously, the problem related with the fact that today started last week of
> the year.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
