[
https://issues.apache.org/jira/browse/LOG4J2-2629?focusedWorklogId=261083&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-261083
]
ASF GitHub Bot logged work on LOG4J2-2629:
------------------------------------------
Author: ASF GitHub Bot
Created on: 17/Jun/19 00:08
Start Date: 17/Jun/19 00:08
Worklog Time Spent: 10m
Work Description: rgoers commented on issue #279: LOG4J2-2629: Avoid
losing log events when the PurgePolicy races a log event
URL: https://github.com/apache/logging-log4j2/pull/279#issuecomment-502497316
You will also have to apply this to release-2.x. As far as I am concerned
you don't need another PR - just commit it.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 261083)
Time Spent: 20m (was: 10m)
> RoutingAppender + purge policy race results in attempts to append to a closed
> appender
> --------------------------------------------------------------------------------------
>
> Key: LOG4J2-2629
> URL: https://issues.apache.org/jira/browse/LOG4J2-2629
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Using the RoutingAppender with an idle timeout policy results in
> intermittently logging:
> {noformat}
> ERROR Attempted to append to non-started appender <name>{noformat}
> Encountered in combination with IdlePurgePolicy.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
