[
https://issues.apache.org/jira/browse/LOG4J2-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852679#comment-16852679
]
ZHU edited comment on LOG4J2-2583 at 5/31/19 5:38 AM:
------------------------------------------------------
Surprisingly, the rollback of wms_bug is normal.
I found that on the same application on another server with fewer logs, the
log rollback during this time is normal. I guess if it is because the log file
is too large, causing the rollback exception.
!image-2019-05-31-13-38-08-550.png!
!image-2019-05-31-13-17-24-108.png!
!image-2019-05-31-13-37-53-171.png!
was (Author: joyce):
Surprisingly, the rollback of wms_bug is normal.
I found that on the same application on another server with fewer logs, the log
rollback during this time is normal. I guess if it is because the log file is
too large, causing the rollback exception.
!image-2019-05-31-13-17-24-108.png!
!image-2019-05-31-13-17-05-461.png!
> The log file is abnormal when configured as RollingFile
> -------------------------------------------------------
>
> Key: LOG4J2-2583
> URL: https://issues.apache.org/jira/browse/LOG4J2-2583
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.11.2
> Reporter: ZHU
> Priority: Critical
> Fix For: 2.12.0
>
> Attachments: catalina.out.bak, image-2019-04-04-11-14-37-293.png,
> image-2019-04-04-11-14-52-646.png, image-2019-05-27-10-56-09-148.png,
> image-2019-05-31-13-11-27-114.png, image-2019-05-31-13-11-41-481.png,
> image-2019-05-31-13-15-41-681.png, image-2019-05-31-13-17-24-108.png,
> image-2019-05-31-13-37-53-171.png
>
>
> The current time is 2019-04-04 11:05
> The log is written to the wms.log.2019-04-03 file instead of the wms.log file.
> !image-2019-04-04-11-14-37-293.png!
> My configuration ：
> !image-2019-04-04-11-14-52-646.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
