Skip to navigation

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

Updated 2013-10-22T18:36:56+00:00

Issue

  • 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.

Environment

  • 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 jboss.server.data.dir was set to /data/eap/default

Subscriber content preview. For full access to the Red Hat Knowledgebase, please log in.

Not a subscriber? Learn more about the benefits of Red Hat Subscriptions.