[
https://issues.apache.org/jira/browse/LOG4J2-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494997#comment-17494997
]
Ralph Goers edited comment on LOG4J2-3361 at 2/19/22, 4:46 PM:
---------------------------------------------------------------
Can you either set the status attribute on the Configuration element to debug
or specify -Dlog4j2.debug=true and then provide the logs from that from when a
rollover fails. I suspect that renaming or copying and deleting the file is
failing. You should see messages for that in your console logs.
I also notice that you do not have a Delete Action configured. As it stands you
will have at most 20 files per day for an unlimited number of days.
was (Author: [email protected]):
Can you either set the status attribute on the Configuration element to debug
or specify -Dlog4j2.debug=true and then provide the logs from that from when a
rollover fails. I suspect that renaming or copying and deleting the file is
failing. You should see messages for that in your console logs.
> SizeBasedTriggeringPolicy does not work properly
> ------------------------------------------------
>
> Key: LOG4J2-3361
> URL: https://issues.apache.org/jira/browse/LOG4J2-3361
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Balaram barada
> Assignee: Ralph Goers
> Priority: Major
>
>
> We have configured log42.xml as given below , its configured as 5MB but
> rolling files are getting generated more then 5Mb i.e 6.3MB ,9 Mb , 5.3 MB
> etc.
>
> {code:java}
> <RollingFile name="INSTALLER_LOG" fileName="${sys:iwloghome}/installer.log"
>
> filePattern="${sys:iwloghome}/installer-%d{yyyy-MM-dd}-%i.log"
> ignoreExceptions="false">
> <PatternLayout pattern ="%-5p | %d{yyyy-MM-dd HH:mm:ss} | [%t] %C{2}
> (%F:%L) - %m%n"/>
> <Policies>
> <SizeBasedTriggeringPolicy size="5MB" />
> </Policies>
> <DefaultRolloverStrategy max="20"/>
> </RollingFile> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
