[ https://issues.apache.org/jira/browse/LOG4J2-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529997#comment-15529997 ]
Remko Popma commented on LOG4J2-1235: ------------------------------------- Sasha, I thought you verified that master worked correctly. What happened? Anyway, if the issue is not actually fixed, please reopen it. > org.apache.logging.log4j.core.appender.routing.IdlePurgePolicy not working > correctly > ------------------------------------------------------------------------------------ > > Key: LOG4J2-1235 > URL: https://issues.apache.org/jira/browse/LOG4J2-1235 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders > Affects Versions: 2.5 > Reporter: Niranjan Rao > Assignee: Gary Gregory > Priority: Critical > Fix For: 2.7 > > > There is a problem in the function > org.apache.logging.log4j.core.appender.routing.IdlePurgePolicy.scheduleNext(). > I got out of file handles errors despite of setting IdlePurgePolicy. I did > some digging I believe following is the cause > If the createTime is Long.MAX_VALUE, task is never scheduled. However > function > org.apache.logging.log4j.core.appender.routing.IdlePurgePolicy.update(String, > LogEvent) checks if the future is not null before deciding to schedule. > After appendersUsage becomes empty first time, appenders keep piling up. > I believe fix will be to set future to null in the function scheduleNext in > the else part of the condition where it checks for createTime -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org