Created attachment 916499 [details] dupe-platform.png Description of problem: See attached screenshot. One of the servers was created with two associated platform instances. It is not possible to monitor both resources after importing the second one discovered: 2013-11-12 17:33:19,267 INFO [InventoryManager.discovery-1] (AutoDiscoveryExecutor)- Discovered new platform with 3 child server(s). 2013-11-12 17:33:19,267 INFO [InventoryManager.discovery-1] (InventoryManager)- Sending [server] inventory report to Server... 2013-11-12 17:33:19,437 WARN [InventoryManager.discovery-1] (AutoDiscoveryExecutor)- Exception caught while executing server discovery scan. [Warning] javax.ejb.EJBTransactionRolledbackException: result returns more than one elements at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:138) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:228) at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:317) at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) at org.rhq.enterprise.server.discovery.DiscoveryBossLocal$$$view100.getResourceSyncInfo(Unknown Source) at org.rhq.enterprise.server.discovery.DiscoveryBossBean.mergeInventoryReport(DiscoveryBossBean.java:237) Version-Release number of selected component (if applicable): 3.2 GA How reproducible: Unclear. The server itself could have been under a lot of load, or some other condition during the upgrade. It seems like OS Platform resource has been imported before upgrading (in 3.1.2), and after that a new Java Platform resource has been discovered as well. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The work-around this problem mostly works: 1) First find the resources for the agent: select * from rhq_resource where agent_id = 14439 order by resource_type_id 2) The Platform resource should appear as resource type in the lower numbers, but be called 'Java' or something. Change the type ID to another type, like '10016' (file system), also set the parent resource ID. Update the row. Then go to the UI and uninventory.
master commit 90794dc7a122a1f519bc7f96fa2078d697a160f5 Author: Jay Shaughnessy <jshaughn> Date: Fri Aug 1 15:09:12 2014 -0400 Add some logging that would have been helpful investigating this issue.
//System.out.println(System.getProperty("os.name").toLowerCase(Locale.US)); java TestProp linux [root@webserver ~]# locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL="
release/jon3.2.x commit abea2375bd42099d4e48237672a6b2e79b04398f Cherry-Pick Master 2a09fd40f5d0b25c5d1c3ba37c553095dc366e60 release/jon3.2.x commit a421d25c5125c8298dca44a28cc2574fbbf2b110 Conflicts: modules/core/native-system/src/main/java/org/rhq/core/system/JavaSystemInfo.java Cherry-Pick master 90794dc7a122a1f519bc7f96fa2078d697a160f5
Moving to ON_QA as this is available for test in JON 3.2.3 ER01 build: http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.3.GA/8-14-14/