[jboss-jira] [JBoss JIRA] (LOGMGR-279) The configuration API removes handler references before the handler is removed from a logger/handler

[James Perkins (Jira)]

     [ https://issues.redhat.com/browse/LOGMGR-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins updated LOGMGR-279:
---------------------------------
    Fix Version/s: 2.2.0.Final
                   2.1.17.Final
                   2.3.0.Beta1


> The configuration API removes handler references before the handler is removed from a logger/handler
> ----------------------------------------------------------------------------------------------------
>
>                 Key: LOGMGR-279
>                 URL: https://issues.redhat.com/browse/LOGMGR-279
>             Project: JBoss Log Manager
>          Issue Type: Bug
>            Reporter: James Perkins
>            Assignee: James Perkins
>            Priority: Critical
>             Fix For: 2.2.0.Final, 2.1.17.Final, 2.3.0.Beta1
>
>
> Using the configuration API to remove a handler from a logger and a handler in the same transaction does not the handler from a logger or a different handler. The handler reference is removed and closed before the attempt to remove the handler from the logger or handler. This ends up leaving the handler on the logger or on the handler so messages are still published to the handler.
> Note too that this could also be an issue with the post configuration actions as they require the handler reference as well.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)