[jboss-jira] [JBoss JIRA] (LOGMGR-261) If a module is defined and the log manager is on boot class path the log manager will fail to configure

If a module is defined and the log manager is on boot class path the log manager will fail to configure ------------------------------------------------------------------------------------------------------- Key: LOGMGR-261 URL: https://issues.jboss.org/browse/LOGMGR-261 Project: JBoss Log Manager Issue Type: Bug Components: core Reporter: James Perkins Assignee: James Perkins Priority: Critical Labels: jdk11 If the log manager is on the boot class path and a module is defined in the {{logging.properties}} or defined in the configuration API the log manager will fail to configure. 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: {code} 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 {code} The only real resolution to this will be to create some kind of {{ModuleFinder}} API in the log manager which allows something like jboss-modules to implement a version which knows how to log the modules.