Description of problem: 1. Upload rhq-switchyard plugin to JON 3.2 Alpha https://github.com/knrc/rhq-switchyard-plugin 2. Install SOA 6 by unzipping the build [1] into an existing EAP 6.1 directory. From the agent log JON JBossAS7 plugin fails to inventory SOA 6. I don't see any discovery attempt by Switchyard plugin. 2013-08-16 13:13:08,058 ERROR [ResourceDiscoveryComponent.invoker.daemon-187] (rhq.modules.plugins.jbossas7.StandaloneASDiscovery)- Discovery of a JBossAS7 Standalone Server Resource failed for process: pid=[11011], name=[java], ppid=[10949]. java.lang.RuntimeException: Failed to determine product type for JBoss product installed at [/home/hudson/jboss-eap6-standalone]. at org.rhq.modules.plugins.jbossas7.JBossProductType.determineJBossProductTypeViaHomeDirName(JBossProductType.java:133) at org.rhq.modules.plugins.jbossas7.JBossProductType.determineJBossProductType(JBossProductType.java:66) at org.rhq.modules.plugins.jbossas7.BaseProcessDiscovery.buildResourceDetails(BaseProcessDiscovery.java:195) at org.rhq.modules.plugins.jbossas7.StandaloneASDiscovery.buildResourceDetails(StandaloneASDiscovery.java:85) at org.rhq.modules.plugins.jbossas7.BaseProcessDiscovery.discoverResources(BaseProcessDiscovery.java:138) --------- [1] SOA http://dev138.mw.lab.eng.bos.redhat.com/candidate/soa-6.0.0.ER1/ file soa-6.0.0.ER1-redhat-1.zip EAP build http://download.devel.redhat.com/released/JBEAP-6/6.1.0/ ---------
The discovery of the server is currently handled by the jboss as7 plugin, the switchyard plugin is only responsible for exposing the SY MBeans through JON. I'll try to reproduce your test and find out why the jboss as7 plugin is not succeeding with the discovery.
Thomas, can you please work with the SOA guys to get this quickly resolved?
Created attachment 788503 [details] proposed patch
Merged patch from Libor in master commit e960b65c053fa58bcb383b09783e2fcc476c9ccd Author: Libor Zoubek <lzoubek> Date: Tue Aug 20 23:05:49 2013 +0200
Hi Kevin, Can you confirm that in JBossProductType class we need to keep: * "SOA-P" as SHORT_NAME * "JBoss SOA-P 6" as NAME * "SOAP" as PRODUCT_NAME SHORT_NAME is used to build default resource name NAME is only used for debugging AFAIK PRODUCT_NAME is used for resource plugin config validation (see org.rhq.modules.plugins.jbossas7.BaseServerComponent#validateServerAttributes and org.rhq.modules.plugins.jbossas7.BaseServerComponent#getAvailabilityNow) Thanks, Thomas
veirified on Version: 4.9.0-SNAPSHOT Build Number: 9bdea14 - SOA instance is discovered.
Verified on Version: 3.2.0.ER4 Build Number: e413566:057b211 Installed SOA 6 by unzipping the build into an existing EAP 6.1 directory. Verified that the soa6 instance is discovered successfully. Please refer the screenshot.
Created attachment 818150 [details] Screenshot