KB-1517 JBoss not starting due to "The logging subsystem requires the log manager" error

Symptoms

When conducting a fresh install of Appian 17.4 and upon starting JBoss the following stack trace is seen:

WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
Jan 23, 2018 8:03:56 PM org.jboss.msc.service.ServiceContainerImpl <clinit>
INFO: JBoss MSC version 1.1.5.Final-redhat-1
Jan 23, 2018 8:03:57 PM org.jboss.as.server.ApplicationServerService start
INFO: JBAS015899: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) starting
Jan 23, 2018 8:03:58 PM org.jboss.as.controller.AbstractOperationContext executeStep
ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([])
java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging
 at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:111)
 at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:702)
 at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:537)
 at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338)
 at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314)
 at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1144)
 at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:393)
 at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:301)
 at org.jboss.as.server.ServerService.boot(ServerService.java:355)
 at org.jboss.as.server.ServerService.boot(ServerService.java:330)
 at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:263)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)
 at java.util.concurrent.FutureTask.get(FutureTask.java:192)
 at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:103)
 ... 11 more
Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
 at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:136)
 at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97)
 at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:139)
 at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:125)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:745)
 at org.jboss.threads.JBossThread.run(JBossThread.java:122)

Cause

This is because the Java agent does not have access to jboss-logmanager classes, so even if the java.util.logging.manager property is set, the classes will not be available.

Action

1. Navigate to <REPO_HOME>/bin/jboss/jboss-eap-6.4/bin.
2. Add the following lines to standalone.custom.sh|bat:
   

   #LogManager java options
   CUSTOM_JAVA_OPTS=$CUSTOM_JAVA_OPTS -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djava.util.logging.manager=org.jboss.logmanager.LogManager CUSTOM_JAVA_OPTS=$CUSTOM_JAVA_OPTS -Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.5.4.Final-redhat-1.jar CUSTOM_JAVA_OPTS=$CUSTOM_JAVA_OPTS -Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.0.2.Final-redhat-1.jar 

3. Using the Configure Script, deploy the changes to JBoss.
4. Restart JBoss.

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018