ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

JBoss Wildfly 10.0 does not stay up after configuring with APM Agent


Article ID: 142656


Updated On:


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


We are running into issues with instrumenting JBoss Wildfly 10.0.  Wildfly starts and so does the JBoss Agent. However after a few minutes, Wildfly exits.


For Windows, a semicolon (;) is required, however on Linux, the semicolon (;) is not translated, therefore Wildfly exits.


Release : 10.7.0 on Linux

Component : APM Agents


We found that there was a semicolon (;) between Final.jar and /opt. Changed that to a colon (:) and restarted. Agent came up and some traffic was introduced. Agent stayed up, application stayed up. 

Original configuration not working:
JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:/opt/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.3.Final.jar;/opt/wildfly/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar"

Working configuration:
JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:/opt/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.3.Final.jar:/opt/wildfly/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar"