Skipping discovery for JBoss AS process
Issue
- JBoss server instance is not discovered by JBoss ON.
- JBoss ON auto-discovery process is detecting incorrect configuration directory - /opt/jboss/at00/server/s0007 and auto-discovery fails with the message in the agent.log file:
Skipping discovery for JBoss AS process process: pid=[3276], name=[/usr/java/jdk1.6.0_24/bin/java], ppid=[3246], because configuration dir '/opt/jboss/at00/server/s0007' does not exist or is not a directory.
Environment
- Red Hat JBoss Operations Network (JON) 3.1.2
- JBoss instance command line looked similar to:
DEBUG [ResourceDiscoveryComponent.invoker.daemon-1] (rhq.plugins.jbossas5.helper.JBossInstanceInfo)- Parsing JBossAS command line [/usr/java/jdk1.6.0_24/bin/java, -Dprogram.name=run.sh, -Djava.rmi.server.hostname=my.host.com, ... -classpath, /opt/jboss/at00/bin/run.jar:/usr/java/jdk1.6.0_24/lib/tools.jar, org.jboss.Main, -c, at00, -P, file:///opt/jboss/at00/properties/startup.properties]...
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
