JON is unable to discover JBoss instance if jboss.server.home.dir is set to a URL

Solution Verified - Updated -

Issue

  • JBoss EAP instance failed to be discovered by JON
  • JBoss EAP instance failed to be discovered by JON agent with the following warning message in the agent log:
    WARN  [ResourceDiscoveryComponent.invoker.daemon-2] (org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent)- Skipping discovery for JBoss AS process process: pid=[12255], name=[java], ppid=[12251], because configuration dir 'file:/opt/jboss/jboss-eap-5.1/jboss-as/server/myConfig' does not exist or is not a directory.
  • Discovery of JBoss AS instance fails indicating the AS configuration directory does not exist or is not a directory

Environment

  • JBoss Operations Network (JON) 2.4.1

  • JON JBoss Application Server (AS) 5 Plug-In

  • JBoss Enterprise Application Platform (EAP) 5.1

  • JBoss AS instance has been started with system property jboss.server.home.dir set to a URL - For example: file:///opt/jboss/jboss-eap-5.1/jboss-as/server/default

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content