[
https://issues.apache.org/jira/browse/LOG4J2-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249630#comment-16249630
]
Ralph Goers edited comment on LOG4J2-2106 at 11/13/17 2:09 PM:
---------------------------------------------------------------
[~rem...@yahoo.com] It seems to me that locking on the checkRollover method
won't be required so long as each TriggeringPolicy only returns true once per
rollover interval. The thing is, I don't know how to accomplish that for the
SizeBasedTriggeringPolicy since it will remain true until the rollover puts a
new file in place. We would need some logic to prevent it from being true twice
and then maybe reset itself when the file size is again less than the max?
was (Author: ralph.go...@dslextreme.com):
[~rem...@yahoo.com] It seems to me that locking on the checkRollover method
won't be required so long as each TriggeringPolicy only returns true once per
rollover interval. The thing is, I don't know how to accomplish that for the
SizeBasedTriggeringPolicy since it will remain true until the rollover puts a
new file in place.
> 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)
