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

Bootable JAR deployments cannot use the System.Logger


      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.

            jperkins-rhn James Perkins
            jperkins-rhn James Perkins
            0 Vote for this issue
            2 Start watching this issue