vshreens opened a new issue, #3475:
URL: https://github.com/apache/logging-log4j2/issues/3475
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:
<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>
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
