Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Critical
Fix Version/s: 2.1.6.Final
Affects Version/s: None
Component/s: Logging
Labels:
- downstream_dependency

Git Pull Request:
https://github.com/jboss-modules/jboss-modules/pull/328, https://github.com/jboss-modules/jboss-modules/pull/329

~~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.

blocks

WFCORE-6721 Do not use reflection to activate System.Logger for Bootable JARs and Embedded servers

Open

is incorporated by

JBEAP-26747 (8.0.z) MODULES-447 - The ModuleLoggerFinder should activate to avoid a runaway queue

Resolved

JBEAP-26746 (7.4.z) MODULES-447 - The ModuleLoggerFinder should activate to avoid a runaway queue

Open

is triggered by

MODULES-441 Lazily initialize System.Logger's in the ModuleLoggerFinder

Resolved

relates to

WFCORE-6712 Bootable JAR deployments cannot use the System.Logger

Resolved

JBEAP-26691 (8.0.z) Bootable JAR deployments cannot use the System.Logger

Closed

JBEAP-26689 (7.4.z) Bootable JAR deployments cannot use the System.Logger

Open

MODULES-367 Bootstrap API

Open

(3 relates to)

Assignee:: James Perkins

Reporter:: James Perkins

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2024/02/23 12:23 AM

Updated:: 2024/04/10 10:39 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates