[
https://issues.apache.org/jira/browse/LOG4J2-2631?focusedWorklogId=261046&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-261046
]
ASF GitHub Bot logged work on LOG4J2-2631:
------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jun/19 19:02
Start Date: 16/Jun/19 19:02
Worklog Time Spent: 10m
Work Description: carterkozak commented on pull request #278:
LOG4J2-2631: RoutingAppender IdlePolicy implementations don't remove …
URL: https://github.com/apache/logging-log4j2/pull/278
…referenced appenders
Note that this makes a behavior change to RoutingAppender.getAppenders
where Routes based on appender references are no longer included.
PurgePolicy implementations should be entirely unaware of the
existance of reference based routes because those appenders may
be used elsewhere in the configuration.
----------------------------------------------------------------
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: 261046)
Time Spent: 10m
Remaining Estimate: 0h
> RoutingAppender purge policy should only stop appenders that the
> RoutingAppender has created
> --------------------------------------------------------------------------------------------
>
> Key: LOG4J2-2631
> URL: https://issues.apache.org/jira/browse/LOG4J2-2631
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.11.2
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Routing to other appenders linked by reference rather than creation by node
> shouldn't cause the purge policy to stop the appender. These appenders should
> probably be immune from purging altogether.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
