[ 
https://issues.apache.org/jira/browse/LOG4J2-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15464308#comment-15464308
 ] 

Sascha Scholz commented on LOG4J2-1235:
---------------------------------------

{noformat}
a82794f06e3bc095ef0bca41b98c5d1ea915de76 is the first bad commit
commit a82794f06e3bc095ef0bca41b98c5d1ea915de76
Author: Gary Gregory <[email protected]>
Date:   Fri Aug 19 17:27:26 2016 -0700

    [LOG4J2-1504] RollingFileAppender should be able to create files
    on-demand.

:040000 040000 3d3faa81429c2ff83db3b1672a2700e2efe770e3 
279da0b08553454f69fdbebfcdb855b21dc7c2ae M      log4j-core
:040000 040000 9548cb83e88b752d42e80ef6cab3463eed9b868c 
5a23c7038b1f4bb49c8b6b8727d4a681db3c2ae8 M      src
{noformat}

> 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
>            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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to