I have been trying to get jopr to see a jboss server as available but running into this issue below showing up in the rhq-agent log file on a RHEL server. I have a link from /opt/jboss pointing to /opt/jboss-eap-4.3 but its getting it confused for some reason. Any ideas?
2009-08-21 10:04:38,026 DEBUG [InventoryManager.discovery-1] (org.rhq.plugins.jbossas.JBossASServerComponent)- Availability check for JBAS resource with conf
igPath [/opt/jboss/jboss-as/server/JBAS01] is trying to connect to a different running JBAS which is installed at [/opt/jboss-eap-4.3/jboss-as/server/JBAS01]. Returning AvailabilityType.DOWN for the former resource.
2009-08-21 10:04:38,026 DEBUG [InventoryManager.discovery-1] (rhq.core.pc.inventory.RuntimeDiscoveryExecutor)- Availability of Resource[id=501582, type=JBoss
AS Server, key=/opt/jboss/jboss-as/server/JBAS01, name=test.com JBossEAP 4.3.0.GA_CP04 JBAS01 (0.0.0.0:1399), parent=test, ver
sion=4.3.0.GA_CP04] is not UP, so we can't execute runtime discovery on it.
This is due to a bug in Jopr 2.2 (https://jira.jboss.org/jira/browse/JOPR-206). The bug has been fixed in trunk and the fix will be included in Jopr 2.3.