-
Title
Failing JBoss7 instrumentation started as a domain -
Description
While instrumenting JBoss EAP in domain mode, it creates the agent logs but no Agents show up on the Monitor dashboard. -
Cause
JBoss agent will look for configuration files under -DJBoss.config.dir whereas in this environment, configuration files are under
-DJBoss.domain.base.dir.
Also, if the files are not available in -DJBoss.config.dir, it will look for the config file (host-slave.xml) under default JBoss Home directory.
This file doesn't have the server/group name, which caused the "incomplete partition name" error in the FMS log, even after specifying
-Dcom.quest.pas.agentinfo.JBoss.partition=ftcdomain and -Dquest.agent.appserverinfo flags.
-
Resolution
WORKAROUND 1:
It is required to pass the -Dquest.agent.nm.pass.agent.appserverinfo flag since the JBoss server is launched by the process controller. Regular -Dquest.agent.appserverinfo flag won't get passed to the launched process. That was the reason, that partitionname was incomplete and as a result, JBoss was not instrumented.
Append the following to the PERFORMASURE_OPTIONS= in the startup script:
-Dquest.agent.nm.pass.agent.appserverinfo=<JBOSS Server name>:JBoss:<JBoss version>:<JBoss clustername>
*Note: Change the variables accordingly.
WORKAROUND 2:
If you see the following error, do this step:
java.io.FileNotFoundException: /JBOSS_install/domain/configuration/host-slave.xml (No such file or directory)
Copy the host-slave.xml from where it currently resides into the directory location mentioned in the error message.
STATUS:
Waiting for fix in a future release of Foglight for JavaEE cartridge.
-
Defect ID
FAPM-579