JON fails to determine JNP URL for JBoss AS resource if AS data directory is not located in the default location

Solution Verified - Updated -


  • No JNP URL is set for newly discovered JBoss AS server
  • JON Agent logs the following warning:

    WARN  [ResourceDiscoveryComponent.invoker.daemon-847] (org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent)- Failed to read JNP URL from '/opt/jboss/eap/jboss-eap-5.1/jboss-as/server/default/data/jnp-service.url'.
    WARN  [ResourceDiscoveryComponent.invoker.daemon-847] (org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent)- Failed to discover JNP URL for JBoss instance with configuration directory [/opt/jboss/eap/jboss-eap-5.1/jboss-as/server/default/].
  • Naming provider URL is not being discovered.


  • Red Hat JBoss Operations Network (ON) 2.4.1, 3.0, 3.1
  • JBoss Enterprise Application Platform (EAP) 5
  • JBoss EAP 5 management plug-in
  • JBoss server's data directory has been relocated to a location other then <JBOSS_HOME>/server/<JBOSS_PROFILE> or the value provided by jboss.server.home.dir -- For example, the system property was set to /data/eap/default

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In