JBossASDiscoveryComponent error
We have seen below error in agent.log of a server.and so JBossAS element is not discovered by JON test.
2017-09-22 10:24:26,110 ERROR [ResourceDiscoveryComponent.invoker.daemon-366] (rhq.plugins.jbossas.helper.JBossInstanceInfo)- Failed to parse argument to --properties option: /opt/posten/isp/rtpi/n1cem/n1cem/rtp001/jboss.e1/isp-consumedservices.properties
2017-09-22 10:24:26,111 WARN [ResourceDiscoveryComponent.invoker.daemon-366] (org.rhq.plugins.jbossas.JBossASDiscoveryComponent)- Skipping discovery for JBoss AS process process: pid=[70990], name=[/opt/posten/isp-1.3.2/isp-1.3.2/jdk1.6.0_45x64/bin/java], ppid=[70957], because configuration dir '/opt/posten/isp/rtpi/n1cem/n1cem/rtp001/jboss.e1/server/as' does not exist or is not a directory.
Responses
You should check if "/opt/posten/isp/rtpi/n1cem/n1cem/rtp001/jboss.e1/server/as" directory exists. Make sure that the user running JBoss ON agent is able to read from this directory.
Double check what values are configured for:
JBOSS_HOME
JBOSS_BASE_DIR
JBOSS_LOG_DIR
JBOSS_CONFIG_DIR
Regards, Biljana.
JBossASDiscoveryComponent is from the EAP 4 plug-in so this message can safely be ignored. Essentially it means that the EAP 4 plug-in attempted to determine if the discovered process was an EAP 4 process and in doing so, failed to read a properties file specified in the JVM command-line. I would not worry too much about it.
There must be a different reason for the application server not being discovered. What application server/version is it and have you verified that you do have the correct plug-ins installed? Perhaps try re-installing the plug-in and ensure that you have either restarted your agent since you the plug-in install/upgrade was completed or used the Update Agent Plugins function from the Agent Topology Configuration Administration page.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.