Uploaded image for project: 'JBoss Modules'
  1. JBoss Modules
  2. MODULES-393

Make jboss-modules a Java agent and allow other agents to be set as module arguments

    XMLWordPrintable

Details

    Description

      The JBoss Log Manager allows for a module to be defined and it uses JBoss Modules to load said module. However if the log manager is on the boot class path, the log manager cannot see JBoss Modules and therefore cannot load the module.

      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

      Making JBoss Modules an agent and allowing other agents to be passed via module arguments avoids the need for the jboss-logmangaer to be on the boot class path. This also will fix issues with the JBoss Logger Finder issue LOGMGR-254.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4674 Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path

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

          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
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4824 Upgrade JBoss Modules from 1.9.2 to 1.10.0.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 related to

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

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4805 WildFly Security Manager does not act for javaagents

          • 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. LOGMGR-254 JDK11, Warning when starting WildFly with logmanager in bootclasspath

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

          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) BYTEMAN-398 Check the entry points class loader before using the system class loader

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: