Created attachment 866045 [details] test war Description of problem: This issue was discovered by automation and I'm not able to reproduce it locally, but system stays in broken state when automation finishes. So I can provide machine in this broken state. Version-Release number of selected component (if applicable): Version : 4.10.0-SNAPSHOT Build Number : bd937f0 How reproducible: Always by automation Steps to Reproduce: 1. go to EAP Domain Controller resource->Inventory->Child Resources 2. Create Child->DomainDeployment 3. use attached war 4. go to Child History Actual results: Create child failed with "An error occured while the agent was uploading the content for [PackageDetailsKey[Name=hello1.war, Version=0 Arch=noarch Type=file]]" Agent log contains following exception: 2014-02-21 09:12:03,351 DEBUG [ResourceContainer.invoker.nonDaemon-4] (rhq.modules.plugins.jbossas7.BaseComponent)- Failed to pull package from server java.lang.NullPointerException at org.rhq.modules.plugins.jbossas7.BaseComponent.deployContent(BaseComponent.java:466) at org.rhq.modules.plugins.jbossas7.HostControllerComponent.createResource(HostControllerComponent.java:121) 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:601) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocation.call(ResourceContainer.java:758) 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:722) Expected results: No errors
*** This bug has been marked as a duplicate of bug 1096332 ***
Reopening, this seems to have a different cause than bug 1096332.
It's actually the same problem. *** This bug has been marked as a duplicate of bug 1096332 ***