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

Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path

    XMLWordPrintable

Details

    Description

      If the log manager is on the boot class path with Java 11, -Xbootclasspath/a:jboss-logmanager.jar, and a custom handler, formatter or filter is used the server will fail to boot as the log manager can't see the types in jboss-modules. This seems due to the fact that the log manager is on the boot class path and jboss-modules is on the system class path.

      Example exception:

      Failed to read or configure the org.jboss.logmanager.LogManager
java.lang.IllegalArgumentException: Failed to load module "org.jboss.logmanager" for formatter "JSON"
    at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:65)
    at org.jboss.logmanager.config.FormatterConfigurationImpl.<init>(FormatterConfigurationImpl.java:30)
    at org.jboss.logmanager.config.LogContextConfigurationImpl.addFormatterConfiguration(LogContextConfigurationImpl.java:172)
    at org.jboss.logmanager.PropertyConfigurator.configureFormatter(PropertyConfigurator.java:631)
    at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:701)
    at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:583)
    at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:521)
    at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97)
    at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:170)
    at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:132)
    at java.util.logging.LogManager$3.run(LogManager.java:399)
    at java.util.logging.LogManager$3.run(LogManager.java:396)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396)
    at java.util.logging.LogManager.access$800(LogManager.java:145)
    at java.util.logging.LogManager$2.run(LogManager.java:345)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338)
    at java.util.logging.LogManager.getLogManager(LogManager.java:378)
    at org.jboss.modules.Main.main(Main.java:523)
Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoader
    at org.jboss.logmanager.config.AbstractPropertyConfiguration$ModuleFinder.getClassLoader(AbstractPropertyConfiguration.java:556)
    at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:63)
    ... 19 more

      Attachments

        1. standalone.conf
          5 kB
        2. standalone.conf
          5 kB
        3. wildfly-bugreport.zip
          42 kB

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. LOGMGR-261 If a module is defined and the log manager is on boot class path the log manager will fail to configure

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

          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-393 Make jboss-modules a Java agent and allow other agents to be set as module arguments

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4899 Upgrade jboss-modules from 1.10.0.Final to 1.10.1.Final

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4676 Upgrade jboss-modules from 1.9.1.Final to 1.10.0.Final

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4675 Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          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) CLOUD-3537 Update startup module / agent loading to not require bootclasspath/a

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

          Feature Request - Feature requests from customers and/or users WFCORE-4748 Expose the ability to add jboss-modules specific arguments

          • 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.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21375 [GSS](7.3.z) Custom handlers cause JBoss EAP 7 to crash if the log manager is on the boot class path

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: