[jboss-jira] [JBoss JIRA] (WFLY-2595) Logging DUP leaking class loaders

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980326#comment-12980326 ] 

RH Bugzilla Integration commented on WFLY-2595:
-----------------------------------------------

mark yarborough <myarboro at redhat.com> changed the Status of [bug 1038305|https://bugzilla.redhat.com/show_bug.cgi?id=1038305] from VERIFIED to CLOSED

> Logging DUP leaking class loaders
> ---------------------------------
>
>                 Key: WFLY-2595
>                 URL: https://issues.jboss.org/browse/WFLY-2595
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>            Reporter: James Perkins
>            Assignee: James Perkins
>            Priority: Critical
>             Fix For: 8.0.0.CR1
>
>
> When a new {{LogContext}} is created for per-deployment logging the class loader is registered as the key. On undeploy the {{LogContext}} should be removed, but the wrong {{LogContext}}t is retrieved due to the caller class loader being used rather than the TCCL.
> The use of the caller class loader is for filtering out system dependencies from the deployment so the correct {{LogContext}} is retrieved from the selector.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)