You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by "Stefan Wehner (JIRA)" <ji...@apache.org> on 2015/01/30 13:26:36 UTC

[jira] [Updated] (LOG4J2-947) A new StatusLoggerAdmin listener is added to StatusLogger everytime the log is reconfigured

     [ https://issues.apache.org/jira/browse/LOG4J2-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Wehner updated LOG4J2-947:
---------------------------------
    Attachment: fix_admin_listeners_leak.patch

This removes all StatusLoggerAdmin registered with the same contextName before registering the new one when reconfiguring the log.

> A new StatusLoggerAdmin listener is added to StatusLogger everytime the log is reconfigured
> -------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-947
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-947
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1
>            Reporter: Stefan Wehner
>            Priority: Minor
>         Attachments: fix_admin_listeners_leak.patch
>
>
> When reconfiguring the log the StatusLogger is also reconfigured and every time this is done a new StatusLoggerAdmin is registered on the StatusLogger even if there was already one for this context.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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