Bug 699893 - [JBoss AS] Discovery fails to determine JNP URL if data directory is not located at ${jboss.server.home.dir}/data
[JBoss AS] Discovery fails to determine JNP URL if data directory is not loca...
Status: ON_QA
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
All All
medium Severity high (vote)
: ---
: ---
Assigned To: John Mazzitelli
Mike Foley
Depends On:
Blocks: 911692
  Show dependency treegraph
Reported: 2011-04-26 16:39 EDT by Larry O'Leary
Modified: 2013-05-13 13:26 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 911692 (view as bug list)
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Legacy) 54752 None None None Never

  None (edit)
Description Larry O'Leary 2011-04-26 16:39:26 EDT
Description of problem:
If a JBoss AS instance has had its data directory relocated or renamed, the JBoss AS plug-in fails to determine a valid Naming Provider URL (JNP URL) for the plug-in configuration for the newly imported resource. 

Version-Release number of selected component (if applicable):
JON 2.4.1

How reproducible:

Steps to Reproduce:
1. Install a fresh EAP server
2. Start it an alternate location for its data directory:
   ./run.sh -c default -b -Djboss.server.data.dir=/tmp/data/eap/default
3. Discover and import the new EAP instance
Actual results:
The AS resource is imported but it is marked DOWN and the JNP URL is not set under <resource> -> Inventory >> Connection. The agent also 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'.

Expected results:
The AS resource is imported and the JNP URL is correct. The value should be read from /tmp/data/eap/default/jnp-service.url

Additional info:
This issue is cause by the assumption that the data directory is fixed or the presence is required by AS. Instead, this value is determined based on configuration of the AS instance itself and if not explicitly set, will default to ${jboss.server.home.dir}/data. The plug-in should not assume the default and instead use the value provided by the system property ${jboss.server.data.dir} and if not set, fall-back to the current behavior.
Comment 1 dsteigne 2013-02-15 09:12:59 EST
Can this be fixed for JON 3.2 release?
Comment 4 Larry O'Leary 2013-02-15 11:33:21 EST
I have cloned this bug to the JBoss ON product bug tracker as bug 911692.
Comment 5 John Mazzitelli 2013-05-10 17:11:02 EDT
I committed a fix to this in master: 8130e34 

I see the JNP URL is discovered now (I see it in the plugin config in the UI) but my initial test showed the server is still DOWN. I don't know if this is because some other part of the plugin code expects the data directory to be in the default location or if it was a local problem on my box only (I was having port conflicts and the problem might be due to that). I'm still testing.
Comment 6 John Mazzitelli 2013-05-13 13:26:25 EDT
I corrected my runtime issue (it was a local problem) and I tested the fix for this BZ. It looks good.

Note You need to log in before you can comment on or make changes to this bug.