-
Bug
-
Resolution: Done
-
Critical
-
None
JBoss Modules installs a java.lang.System.LoggerFinder when used. In it's main entry point it activates this logger finder by executing ModuleLoggerFinder.activate(). However, the bootable JAR does not use JBoss Modules' entry point so this never gets invoked. This leaves the ModuleLoggerFinder in a state of always queuing messages. If a module or deployment attempts to use a System.Logger, the message will never be seen.
This could also lead to a crash if the queue of messages is over loaded.
The issue was introduced in MODULES-441. The ModuleLoggerFinder doesn't take into account that it may never have it's activate method invoked. It was assumed entry points always happen from org.jboss.modules.Main, however that is not the case.
- clones
-
JBEAP-26689 (7.4.z) Bootable JAR deployments cannot use the System.Logger
- Open
- depends on
-
JBEAP-26748 [8.0.z] Upgrade jboss-modules to 2.1.2
- Closed
- is blocked by
-
JBEAP-26758 [GSS](8.0.z) Upgrade jboss-modules from 2.1.3.Final-redhat-00001 to 2.1.4.Final-redhat-00001
- Closed
- is caused by
-
MODULES-441 Lazily initialize System.Logger's in the ModuleLoggerFinder
- Resolved
- is incorporated by
-
JBEAP-25379 (8.0.z) Upgrade WildFly Core from 21.0.5.Final-redhat-00001 to 21.0.6.Final-redhat-00001
- Closed
- is related to
-
JBEAP-26747 (8.0.z) MODULES-447 - The ModuleLoggerFinder should activate to avoid a runaway queue
- Resolved
-
MODULES-447 The ModuleLoggerFinder should activate to avoid a runaway queue
- Pull Request Sent