Details
-
Bug
-
Status: Reopened
-
Major
-
Resolution: Unresolved
-
2.9.1
-
None
-
None
Description
My log file is very large, so I set the config about compression. The policies is as follows:
<Policies>
<OnStartupTriggeringPolicy/>
<TimeBasedTriggeringPolicy/>
</Policies>
When restart the service on the hour, this will trigger the two policies. And I find that the log can not be written for a while.
I think, there would be two compress actions. In the file RollingFileManager(package org.apache.logging.log4j.core.appender.rolling), the actions will submit to asyncExecutor which will create a new thread for every work. That mean the log file will be compressed by the two actions. Is this the cause?
Thanks.
Attachments
Issue Links
- relates to
-
LOG4J2-2125 Deadlock bug
- Closed