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

Modules may create loggers on a deployments log context

    XMLWordPrintable

Details

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

    Description

      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.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-11687 FuseOnEAP - Application logs of one application are logged to application logs of another application using EAP's Logging Profiles

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Feature Request - Feature requests from customers and/or users WFCORE-4807 Add option to route log messages based on the current thread's class loader

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Feature Request - Feature requests from customers and/or users LOGMGR-264 Allow logger nodes to be used on different log contexts

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Pull Request Sent

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) LOGMGR-180 Create new LogContextSelector which selects the first caller that is not a log API

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4806 Upgrade jboss-logmanager from 2.1.15.Final to 2.2.0.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated: