]
Jeff Mesnil updated WFCORE-3376:
--------------------------------
Fix Version/s: 11.0.0.Beta9
(was: 11.0.0.Beta8)
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
Fix For: 11.0.0.Beta9
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.