Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3376

Modules may create loggers on a deployments log context

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Logging
    • None

      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.

              jperkins-rhn James Perkins
              jperkins-rhn James Perkins
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: