Uploaded image for project: 'JBoss Modules'
  1. JBoss Modules
  2. MODULES-447

The ModuleLoggerFinder should activate to avoid a runaway queue

    XMLWordPrintable

Details

    Description

      The ModuleLoggerFinder.activate() method should be made public so that it can be invoked from other entry points like the WildFly Bootable JAR.

      MODULES-367 should introduce an API to handle the activation. However, if activation is not done something should happen to the message queue so that it does not fill up.

      As part of this a threshold of messages should used and if that threshold is hit, activation should happen delegating to JUL.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-6721 Do not use reflection to activate System.Logger for Bootable JARs and Embedded servers

          • 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
          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-26746 (7.4.z) MODULES-447 - The ModuleLoggerFinder should activate to avoid a runaway queue

          • Critical - To be worked on immediately following BLOCKER issues.
          • Pull Request Sent

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-26747 (8.0.z) MODULES-447 - The ModuleLoggerFinder should activate to avoid a runaway queue

          • Critical - To be worked on immediately following BLOCKER issues.
          • Pull Request Sent
          is triggered by

          Bug - A problem that impairs or prevents the functions of the product. MODULES-441 Lazily initialize System.Logger's in the ModuleLoggerFinder

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-26691 (8.0.z) Bootable JAR deployments cannot use the System.Logger

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-6712 Bootable JAR deployments cannot use the System.Logger

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-26689 (7.4.z) Bootable JAR deployments cannot use the System.Logger

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open

          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) MODULES-367 Bootstrap 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.
          • Open

          Activity

            People

              jperkins-rhn James Perkins
              jperkins-rhn James Perkins
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: