Description of problem: I cannot add JVM Definition child resource to new managed server. ResourceChildHistory shows 'In progress' .. and finishes after 11 minutes. After that jvm child resource is not discovered Version-Release number of selected component (if applicable): JON 3.2.ER3 + EAP 6{0,1,2} How reproducible: always Steps to Reproduce: 1. have Domain controller 2. create new managed server, do not start it 3. create JVM Definition child resource for your managed server Actual results: ResourceChildHistory shows 'In progress' .. and finishes after 11 minutes, after that JVM is not discovered In agent log .. I meet this WARN [ResourceFactory.executor-1] (rhq.core.pc.inventory.CreateResourceRunner)- Failed to discover Resource for newly created [ResourceType[id=0, name=JVM Definition, plugin=JBossAS7, category=Service]] managed resource with key [host=master,server-config=666,jvm=jvmmm]. Expected results: JVM Definition is created and discovered instantly Additional info: This must be some regression, I can confirm this issue could not be reproduced on JON 3.2.Alpha58. Unfortunately, I don't have results from previous ER builds, because of UI changes, some tests including this did not run at all.
Could not reproduce on a fresh master build. Can you detail the reproduction steps? Did you create another JVM Definition (other than the "default" one) before overriding it in the Managed Server? Now trying on a release/jon3.2.x build...
I have no other steps. I have only default JVM definition. There is one thing, although. I run it on JON 3.2 with all plugins, and I see lots of error messages caused by switchyard plugin Bug 1018270. As those errors happen in discovery, it might be reason for this bug. I tried to reproduce it again .. and even adding managed server took 3minutes, and adding JVM under it took 11 minutes Is it possible that create-child-operation might be blocked by service discovery scan?
Fixed in master commit 71556e140266f819f97342b24f40aaa9ace6ffd0 Author: Thomas Segismont <tsegismo> Date: Thu Nov 7 11:19:09 2013 +0100 Managed server discovery/create did not return consistent resource key formats. So the resource creation process of the Managed Server was stuck and prevented the JVM Definition creation process from starting.
Cherry-picked to release/jon3.2.x commit f1a7c8630e7cc64ae1219efb63bb1009d27529df Author: Thomas Segismont <tsegismo> Date: Thu Nov 7 11:19:09 2013 +0100
Moving to ON_QA as available for testing with new brew build.
Mass moving all of these from ER6 to target milestone ER07 since the ER6 build was bad and QE was halted for the same reason.
verified on ER7