RHQ 4.7 - Error discovering JBoss AS 7.1.1 resource
pathduck May 8, 2013 11:50 AMHi,
not sure if 4.7 is "official" yet but I noticed it was on Sourceforge so figured I'd test it
Anyway, after install a new JBoss server was started, and 4.7 fails in the discovery with the following error:
2013-05-08 16:15:00,960 ERROR [ResourceDiscoveryComponent.invoker.daemon-1] (rhq.modules.plugins.jbossas7.StandaloneASDiscovery)- Discovery of a JBossAS7 Standalone Server Resource failed for process: pid=[15918], name=[/opt/jboss/java/bin/java], ppid=[15867]. java.lang.RuntimeException: Failed to determine product type for JBoss product installed at [/opt/jboss]. at org.rhq.modules.plugins.jbossas7.JBossProductType.determineJBossProductTypeViaHomeDirName(JBossProductType.java:138) at org.rhq.modules.plugins.jbossas7.JBossProductType.determineJBossProductType(JBossProductType.java:67) at org.rhq.modules.plugins.jbossas7.BaseProcessDiscovery.buildResourceDetails(BaseProcessDiscovery.java:196) at org.rhq.modules.plugins.jbossas7.StandaloneASDiscovery.buildResourceDetails(StandaloneASDiscovery.java:85) at org.rhq.modules.plugins.jbossas7.BaseProcessDiscovery.discoverResources(BaseProcessDiscovery.java:139) at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:294) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)
For all the other servers on the system the same error is output, but these have actually been Imported earlier.
Is this a known bug, was I too quick in trying out 4.7 ?
This is quite a big thing, if autodiscovery fails for all new JBoss AS7.
EDIT: Could it be related to RHQ 4.7 running under JBoss EAP 6.1 Alpha? It seems the most logical explanation so far.