logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Zvolinsky (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4J2-1235) org.apache.logging.log4j.core.appender.routing.IdlePurgePolicy not working correctly
Date Fri, 19 Aug 2016 16:04:20 GMT

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

Aleksey Zvolinsky edited comment on LOG4J2-1235 at 8/19/16 4:03 PM:

I was able to apply patch using TortoisGit without any issues. Can you try it?

was (Author: aleksey zvolinsky):
I was able to apply patch using TortoisGit without any issues

> 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
> 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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message