I installed JON 3.2.ER02 - copy all the *.jar plugins from jon-plugin-pack-jpp-3.2.0.ER2 into JON-server/plugins, install and start the server. Downloaded and start rhq-agent. JPP is running and is discovered by JON-server, I imported it from discovery queue. In the rhq-agent log, there appears an InvalidPluginConfigurationException: org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Failed to start component for resource Resource[id=10002, uuid=f4d26827-242a-4c1a-aeb2-4f754bde1689, type={JBossAS7}JBossAS7 Standalone Server, key=hostConfig: /home/mgottval/GateIn/jboss-jpp-6.1/standalone/configuration/standalone.xml, name=JPP (127.0.0.1:9990), parent=localhost.localdomain, version=JPP 6.1.0]. at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:1937) at org.rhq.core.pc.inventory.InventoryManager.updatePluginConfiguration(InventoryManager.java:642) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.rhq.enterprise.communications.command.impl.remotepojo.server.RemotePojoInvocationCommandService.execute(RemotePojoInvocationCommandService.java:184) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:226) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:251) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:857) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:795) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:305) at $Proxy0.execute(Unknown Source) at org.rhq.enterprise.communications.command.server.CommandProcessor.handleIncomingInvocationRequest(CommandProcessor.java:290) at org.rhq.enterprise.communications.command.server.CommandProcessor.invoke(CommandProcessor.java:184) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:967) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:586) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234) Caused by:org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: The original product type discovered for this AS7 server was JBoss JPP 6, but the server is now reporting its product type is [JBoss EAP 6]. at org.rhq.modules.plugins.jbossas7.BaseServerComponent.validateServerAttributes(BaseServerComponent.java:220) at org.rhq.modules.plugins.jbossas7.BaseServerComponent.getAvailabilityNow(BaseServerComponent.java:154) at org.rhq.modules.plugins.jbossas7.BaseServerComponent.getAvailability(BaseServerComponent.java:139) at org.rhq.modules.plugins.jbossas7.BaseServerComponent.start(BaseServerComponent.java:101) at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocation.call(ResourceContainer.java:654) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679)
*** This bug has been marked as a duplicate of bug 856845 ***
Can you please run this command in your test JPP server CLI? [standalone@localhost:9999 /] :read-attribute(name=product-name) The outcome should be: { "outcome" => "success", "result" => "Portal Platform" } But I suspect it will be : { "outcome" => "success", "result" => "EAP" } In this case, please check with JPP engineering team why.
Fixed in master commit 02ed9c403f3ee1aa7fb1b5f1e1cee5713997fa56 Author: Thomas Segismont <tsegismo> Date: Thu Oct 3 12:08:12 2013 +0200 Removed unused EPP entry which prevented deterministic constant look-up by product-name value
Moving to ER4 as pushed after ER3 cutoff and not beta blocker.
Moving to ON_QA for testing in the next build.
Verified with JON 3.2.ER04 + JPP 6.1.CR03.