Created attachment 916709 [details] eap-war-content-missing Description of problem: [eap6 ] cannot create deployment resource - broken after restart Version-Release number of selected component (if applicable): rhq 4.12 master - build id: 1a62d13 How reproducible: 2 of 2 Steps to Reproduce: 1. install eap6 and inventory into server gui 2. create deployment child helloworld.war 3. try creating deployment child helloworld-1.2.war 4. try creating deployment child iBook.war 5. restart EAP6 server Actual results: After step4. no other deployment child can be created - no request sent to EAP, no exception in agent and server logs After step5. EAP6 cannot be started Expected results: After step4. other war deployment child resource can be created Content of hellowrold.war is not broken After step5. eap6 starts without issues Additional info: screen-shots attached
Created attachment 916710 [details] war-deployment-failed
After a quick debuggine session, I was not able to upload any deployment at all (2st step failing) It always fails in AS7 plugin on NPE ContentContext cctx = context.getContentContext(); ResourcePackageDetails details = report.getPackageDetails(); ContentServices contentServices = cctx.getContentServices(); contentServices is NULL
If the bug happens after clean build/installation it keeps repeating and stays there forever, but for some clean builds/installations it doesn't start happening. Here is my environment where the bug is present: https://dl.dropboxusercontent.com/u/14869330/dev-container.zip https://dl.dropboxusercontent.com/u/14869330/pg_dump.output Paths in "rhq-server/rhq-storage/conf/cassandra.yaml" need to be changed properly. This issue is a consequence of ResourceContexts not being fully initialized. There is a PR from Lukas addressing this issue [1]. [1]: https://github.com/rhq-project/rhq/pull/32
Ok, one interesting fact is that the build is supposed to be 1a62d13, which is RHQ 4.12-SNAPSHOT, but the provided environment contains 4.13.0-SNAPSHOT jars in agent's lib. This leads me to believe this might either be a broken build or a broken agent upgrade situation.
The provided server is 4.13.0-SNAPSHOT, too. So this might not be the build advertised. Will investigate with the provided build anyway.
*** This bug has been marked as a duplicate of bug 1125343 ***