DefaultRolloverStrategy creating rolled over log files more than the configured limit

[vshreens]

Hi,

We are using the log4j version 2.24.3 and have an observation where the rolling over of the log files was not in control and rolled over numbering went beyond the configured limit as the logs were getting generated continuously.

Log4j configuration used in application:

Rolled over logs:
$ ls -alhtr test.log*
26M Feb 15 13:02 test.log.33075973
26M Feb 15 13:02 test.log.33075972
26M Feb 15 13:02 test.log.33075971
26M Feb 15 13:02 test.log.33075970
$ ls -alhtr test.log*
26M Feb 15 13:02 test.log.33075979
26M Feb 15 13:02 test.log.33075978
26M Feb 15 13:02 test.log.33075977
26M Feb 15 13:02 test.log.33075976

We wanted to understand if there is any known issue that is causing this or reported already in log4j 2.24.3. Thanks.

[ppkarwasz]

@vshreens,

Can you add your configuration snippet as text, so we can test it?

[vshreens]

Please find it below: I was unable to paste it properly in text format in the earlier message.

    <RollingFile name="test" fileName="test.log" filePattern="test.log.%i" append="true" immediateFlush="true">
        <PatternLayout>
            <pattern>%d{YYYY-MM-dd'T'HH:mm:ss.SSSSSSXXX}, %level{FATAL=crit, WARN=warning, DEBUG=debug, ERROR=err, INFO=info},  , [%t] [%c:%M:%L] | %m%n</pattern>
        </PatternLayout>
        <Policies>
            <SizeBasedTriggeringPolicy size="25 MB" />
        </Policies>
        <DefaultRolloverStrategy fileIndex="min" max="4">
            <Delete basePath="LOG_PATH" maxDepth="1">
                <IfFileName glob="test.log.*">
                    <IfAny>
                        <IfAccumulatedFileSize exceeds="300 MB" />
                    </IfAny>
                </IfFileName>
            </Delete>
        </DefaultRolloverStrategy>
    </RollingFile>

[ppkarwasz]

@vshreens,

Your configuration snippet seems to work correctly. Are you sure you don't have a different RollingFile appender configured to write to test.log, but with different configuration options? Are you restarting your application after a modification to the triggering policies and rollover strategy? Changes to those values are not taken into account during a reconfiguration event, unless you also change the file name.