[ https://issues.jboss.org/browse/WFCORE-254?page=com.atlassian.jira.plugin... ] 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. -- This message was sent by Atlassian JIRA (v6.3.11#6341)