[jboss-jira] [JBoss JIRA] (WFCORE-254) logging-profiles doesn't work with Apache Common Logging

[James Perkins (JIRA)]

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

James Perkins commented on WFCORE-254:
--------------------------------------

The issue is again with jcl-over-slf4j. At this point we might need to fork it.

jcl-over-slf4j uses a static instance and a map to find the logger. Because of this a logger with the same name will return the first logger created no matter which log context it was created on.

For a workaround you should be able exclude org.apache.commons.logging with a jboss-deployment-structure.xml and include a jcl-over-slfj4 library in each WAR deployment.

Note this issue will only appear if loggers with the same name are desired on deployments that use a new log context. For example per-deployment logging that uses commons-logging or logging-profiles that use commons-logging.

> logging-profiles doesn't work with Apache Common Logging
> --------------------------------------------------------
>
>                 Key: WFCORE-254
>                 URL: https://issues.jboss.org/browse/WFCORE-254
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Anders Welen
>            Assignee: James Perkins
>            Priority: Minor
>         Attachments: 87905.tar
>
>
> The logging for one logging-profile ends up in another logging-profile from time to time. It's not sporadic as all logging will end up in the wrong place when things go wrong.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)