[jboss-jira] [JBoss JIRA] (WFCORE-3376) Modules may create loggers on a deployments log context

[James Perkins (Jira)]

    [ https://issues.redhat.com/browse/WFCORE-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976726#comment-13976726 ] 

James Perkins commented on WFCORE-3376:
---------------------------------------

I went ahead and removed the fix version for this. The RFE EAP7-1420 is in a state which could potentially become stalled which would require a different approach for this fix. Until those decisions are made we should not commit to a release.

> Modules may create loggers on a deployments log context
> -------------------------------------------------------
>
>                 Key: WFCORE-3376
>                 URL: https://issues.redhat.com/browse/WFCORE-3376
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>            Reporter: James Perkins
>            Assignee: James Perkins
>            Priority: Critical
>
> Currently WildFly uses a {{ClassLoaderLogContextSelector}} to determine the log context to use when creating loggers. If a deployment has it's own log context, via logging-profile or per-deployment logging, and a dependency on a module, that module may create loggers on the deployments log context. This is due to the fact the the call stack is walked until it finds a log context associated with a class loader.
> What is needed is a way to short-circuit once a non-logging API class loader is found and determine if there is an associated log context with the callers class loader.



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