You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "John Knight (JIRA)" <ji...@apache.org> on 2019/05/20 09:48:01 UTC

[jira] [Created] (LOG4J2-2608) DefaultRolloverStrategy fileIndex="nomax" is ignored

John Knight created LOG4J2-2608:
-----------------------------------

             Summary: DefaultRolloverStrategy fileIndex="nomax" is ignored
                 Key: LOG4J2-2608
                 URL: https://issues.apache.org/jira/browse/LOG4J2-2608
             Project: Log4j 2
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 2.11.2
         Environment: Tomcat 8.5.34 on Windows Server 2012 R2 Standard
            Reporter: John Knight
         Attachments: log4j2.xml

With log size limited to 100Mb we found we were losing log data at the start of the day (originally using version 2.1 since 2016).  So, noticing we were out of date we upgraded to 2.11.2 and added the fileIndex="nomax"  attribute for DefaultRolloverStrategy; config file attached.

We are still finding the log files are restricted to 7 per day in production with consequent loss of data in the early hours of the day.  The same web application in the UAT environment appears to work and can create more than 7 logs per day, but volume is a tiny fraction of production so log size was set to 100KB to test in UAT.

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)