Sangeetha Hariharan created CLOUDSTACK-4464:
-----------------------------------------------
Summary: Parallel deployment - Vmware - When deploying 30 parallel
Vms , Vm fails to get deployed due to "StartCommand failed due to Exception:
javax.xml.ws.soap.SOAPFaultException"
Key: CLOUDSTACK-4464
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4464
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Build from 4.2-forward
Reporter: Sangeetha Hariharan
Priority: Blocker
Fix For: 4.2.1
Parallel deployment - Vmware - When deploying 30 parallel Vms , Vm fails to get
deployed due to "StartCommand failed due to Exception:
javax.xml.ws.soap.SOAPFaultException"
Steps to reproduce the problem:
Set up - Advanced zone with 1 Vmware 5.0.0 Esxi host.
Deploy 30 Vms in parallel.
5 out of 30 vms deployed in parallel , fail due to
"javax.xml.ws.soap.SOAPFaultException".
Management server logs shows the following exception:
2013-08-22 15:57:22,603 WARN [vmware.resource.VmwareResource]
(DirectAgent-91:10.223.58.66) StartCommand failed due to Exception:
javax.xml.ws.soap.SOAPFaultException
Message: The object has already been deleted or has not been completely created
javax.xml.ws.soap.SOAPFaultException: The object has already been deleted or
has not been completely created
at
com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
at
com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
at $Proxy81.retrieveProperties(Unknown Source)
at
com.cloud.hypervisor.vmware.util.VmwareClient.retrieveMoRefProperties(VmwareClient.java:271)
at
com.cloud.hypervisor.vmware.util.VmwareClient.getDynamicProperty(VmwareClient.java:226)
at
com.cloud.hypervisor.vmware.mo.BaseMO.getCustomFieldValue(BaseMO.java:129)
at com.cloud.hypervisor.vmware.mo.HostMO.loadVmCache(HostMO.java:528)
at
com.cloud.hypervisor.vmware.mo.HostMO.findVmOnHyperHost(HostMO.java:488)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2667)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:514)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
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 message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
