[ https://issues.apache.org/jira/browse/LOG4J2-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258274#comment-16258274 ]
Ralph Goers commented on LOG4J2-2106: ------------------------------------- OK. I will look into that. > May blocked when two compress action > ------------------------------------ > > Key: LOG4J2-2106 > URL: https://issues.apache.org/jira/browse/LOG4J2-2106 > Project: Log4j 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.9.1 > Reporter: skopt > > 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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)