JBoss EAP 7.x domain fails to start the hosted servers after disabling jmx in agent profile.

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)
• INTROSCOPE

Issue/Introduction

JBoss EAP 7.x domain fails to start the hosted servers after disabling jmx monitoring in agent profile (introscope.agent.jmx.enable=false)

The other relevant setting was found to be that auto agent naming was also disabled (introscope.agent.agentAutoNamingEnabled=false)

After redirecting the domain.sh console output to a file using command "nohup ./domain.sh > boot.log 2>&1 &" these errors were visible in the boot.log:

Controller-threads - 3) WFLYPC0018: Starting process 'Server:server-one'
[0m[Server:server-one] WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
[Server:server-one] Exception in thread "main" java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
[Server:server-one]     at org.jboss.logmanager.Logger.getLogger(Logger.java:57)
[Server:server-one]     at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:93)
[Server:server-one]     at org.jboss.modules.Module.run(Module.java:344)
[Server:server-one]     at org.jboss.modules.Main.main(Main.java:519)
[0m09:48:34,310 INFO  [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) WFLYPC0011: Process 'Server:server-one' finished with an exit status of 1

Environment

APM 10.5.x, JBoss EAP 7.1

Cause

With jmx and auto agent naming disabled JBoss encountered the known JBoss LogManager error documented in the APM 10.5 wiki i.e.

JBoss Application Server Logging Considerations

Resolution

After original steps for JBoss EAP Domain agent config Configure JBoss EAP in Domain mode, follow the additional steps documented in JBoss Application Server Logging Considerations 

Using the JBoss Management Console e.g. http://hostname/9990/console/App.html#home the steps with 7.1 specific jar fileanames are:
1. Runtime-> Hosts > Master > Properties
With boot flag set:
a. Remove the existing jboss.modules.system.pkgs property and add jboss.modules.system.pkgs=org.jboss.logmanager,com.wily,com.wily.*
b. Add new property java.util.logging.manager=org.jboss.logmanager.LogManager

2. Runtime-> Hosts > Master > JVM
Edit and under  "jvm options"  add additional property:
-Xbootclasspath/p:/root/EAP-7.1.0/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.6.Final-redhat-1.jar:/root/EAP-7.1.0/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.3.Final-redhat-1.jar