[
https://issues.jboss.org/browse/LOGMGR-167?page=com.atlassian.jira.plugin...
]
James Perkins commented on LOGMGR-167:
--------------------------------------
Okay. That would be why a logging profile does not work for them then. A logging profile
only works on deployments because it uses the deployments class loader. Modules would have
their own class loaders. Basically anything logged from the deployment itself should use
the logging profile. Any modules should use the system log context.
Enable fallback on thread context ClassLoader for log context
scanning
----------------------------------------------------------------------
Key: LOGMGR-167
URL:
https://issues.jboss.org/browse/LOGMGR-167
Project: JBoss Log Manager
Issue Type: Enhancement
Reporter: James Netherton
{{ClassLoaderLogContextSelector}} searches the call stack for a {{ClassLoader}}
that's used as a map key to discover the appropriate {{LogContext}}.
If the search fails, can we add an additional check that uses the
ThreadContextClassLoader to lookup the {{LogContext}} from the {{contextMap}}?
My reasoning for requesting this is described in this issue:
https://github.com/wildfly-extras/wildfly-camel/issues/1919#issuecomment-...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)