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

Nick Vigilante — Wed, 28 Feb 2018 21:26:37 GMT

Current Revision posted to Appian Knowledge Base by Nick Vigilante on 2/28/2018 9:26:37 PM

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

Navigate to <REPO_HOME>/bin/jboss/jboss-eap-6.4/bin.

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

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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

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

Nick Vigilante — Thu, 01 Feb 2018 08:03:13 GMT

Revision 13 posted to Appian Knowledge Base by Nick Vigilante on 2/1/2018 8:03:13 AM

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

Navigate to <REPO_HOME>/bin/jboss/jboss-eap-6.4/bin.

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

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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

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

Nick Vigilante — Thu, 01 Feb 2018 08:02:56 GMT

Revision 12 posted to Appian Knowledge Base by Nick Vigilante on 2/1/2018 8:02:56 AM

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

Navigate to <REPO_HOME>/bin/jboss/jboss-eap-6.4/bin.

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

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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

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

Parmida Borhani — Wed, 31 Jan 2018 21:49:24 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 1/31/2018 9:49:24 PM

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

Navigate to <REPO_HOME>/bin/jboss/jboss-eap-6.4/bin.
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

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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

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

Parmida Borhani — Wed, 31 Jan 2018 21:47:34 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 1/31/2018 9:47:34 PM

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

Navigate to <REPO_HOME>/bin/jboss/jboss-eap-6.4/bin.
Add the following line 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

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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

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

Parmida Borhani — Wed, 31 Jan 2018 21:47:16 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 1/31/2018 9:47:16 PM

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

Navigate to <REPO_HOME>/bin/jboss/jboss-eap-6.4/bin.
Add the following line 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

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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

DRAFT KB-XXXX JBoss not starting due to "The logging subsystem requires the log manager" Error

Stephen Okala — Wed, 31 Jan 2018 14:01:36 GMT

Revision 8 posted to Appian Knowledge Base by Stephen Okala on 1/31/2018 2:01:36 PM

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

This change is to be made in the configure script(standalone.custom.sh|bat) repository <REPO_HOME>/bin/jboss/jboss-eap-6.4/bin then deployed to JBoss and finally, restart Jboss.

#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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

DRAFT KB-XXXX JBoss not starting due to "The logging subsystem requires the log manager" Error

Stephen Okala — Wed, 31 Jan 2018 11:17:51 GMT

Revision 7 posted to Appian Knowledge Base by Stephen Okala on 1/31/2018 11:17:51 AM

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

This change is to be made in the configure script(standalone.custom.sh|bat) repository <JBOSS_HOME>/bin then deployed to JBoss and finally, restart Jboss.

#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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

DRAFT KB-XXXX JBoss not starting due to "The logging subsystem requires the log manager" Error

Parmida Borhani — Wed, 31 Jan 2018 00:00:00 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 1/31/2018 12:00:00 AM

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

Add the following to the standalone.custom.sh|bat file, which can be found in <JBOSS_HOME>/bin.

#LogManager java options

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

DRAFT KB-XXXX JBoss not starting due to "The logging subsystem requires the log manager" Error

Parmida Borhani — Tue, 30 Jan 2018 23:59:24 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 1/30/2018 11:59:24 PM

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

Add the following to the standalone.custom.sh|bat file, which can be found in <JBOSS_HOME>/bin.

#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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

DRAFT KB-XXXX JBoss not starting due to "The logging subsystem requires the log manager" Error

Stephen Okala — Tue, 30 Jan 2018 10:06:47 GMT

Revision 4 posted to Appian Knowledge Base by Stephen Okala on 1/30/2018 10:06:47 AM

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

Add the following to the standalone.custom.sh|bat file, which can be found in "JBOSS_HOME\bin"

#LogManager java options

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

DRAFT KB-XXXX JBoss not starting due to "The logging subsystem requires the log manager" Error

Stephen Okala — Tue, 30 Jan 2018 10:05:47 GMT

Revision 3 posted to Appian Knowledge Base by Stephen Okala on 1/30/2018 10:05:47 AM

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

Add the following to the standalone.custom.sh|bat file, which can be found in "JBOSS_HOME\bin"

#LogManager java options

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

DRAFT KB-XXXX JBoss not starting due to "The logging subsystem requires the log manager" Error

Stephen Okala — Mon, 29 Jan 2018 16:07:12 GMT

Revision 1 posted to Appian Knowledge Base by Stephen Okala on 1/29/2018 4:07:12 PM

Symptoms

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

Cause

Currently unknown

Action

Add the following to your standalone.custom.sh (this is inside JBOSS_HOME\bin):

#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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss

DRAFT KB-XXXX JBoss not starting due to "The logging subsystem requires the log manager" Error

Stephen Okala — Mon, 29 Jan 2018 11:21:24 GMT

Revision 2 posted to Appian Knowledge Base by Stephen Okala on 1/29/2018 11:21:24 AM

Symptoms

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

Cause

Currently unknown

Action

Add the following to your standalone.custom.sh (this is inside JBOSS_HOME\bin):

#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

Affected Versions

This article applies to Appian 17.4.

Last Reviewed: January 2018

Tags: engines, installation, jboss