Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Critical
Fix Version/s: None
Affects Version/s: None
Component/s: Modules
Labels:
- regression-test-only
- triaged

Blocked:
False
Blocked Reason:
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
-
Target Release:

8.0.z.GA
Git Pull Request:
https://github.com/jboss-modules/jboss-modules/pull/328
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

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.

clones

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

Open

incorporates

MODULES-447 The ModuleLoggerFinder should activate to avoid a runaway queue

Pull Request Sent

is incorporated by

JBEAP-26795 (8.0.z) Upgrade jboss-modules from 2.1.4.Final-redhat-00001 to 2.1.5.Final-redhat-00001

Resolved

relates to

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

Closed

Assignee:: Lin Gao

Reporter:: Lin Gao

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2024/03/07 5:57 AM

Updated:: 2024/06/10 1:12 PM

Resolved:: 2024/06/04 2:06 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates