cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damodar Reddy Talakanti" <damoder.re...@citrix.com>
Subject Re: Review Request 16153: Fixing by chanding the constructor of MigrateWithStorageAnswer not to include stack trace in the details.
Date Tue, 10 Dec 2013 12:07:05 GMT


> On Dec. 10, 2013, 11:57 a.m., Sateesh Chodapuneedi wrote:
> > Can you please share the exception messages observed in testing against exception
messages printed in web UI earlier?


Exception stack trace is there at defect https://issues.apache.org/jira/browse/CLOUDSTACK-4597..
For the full trace you can go there..


2013-09-02 23:16:34,439 ERROR [storage.motion.VmwareStorageMotionStrategy] (Job-Executor-99:job-175
= [ ca1a7028-1aac-44c0-9833-96cb9f911cde ]) copy failed
com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm VM[User|instance5]
to host Host[-8-Routing]. Exception: javax.xml.ws.WebServiceException
Message: java.net.SocketTimeoutException: Read timed out
Stack: javax.xml.ws.WebServiceException: java.net.SocketTimeoutException: Read timed out
        at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.readResponseCodeAndMessage(HttpClientTransport.java:201)
        at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:151)
        at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:83)
        at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:78)
        at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:587)
        at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:546)
        at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:531)
        at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:428)
        at com.sun.xml.internal.ws.client.Stub.process(Stub.java:211)
        at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:124)
        at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98)
        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 $Proxy89.waitForUpdates(Unknown Source)
        at com.cloud.hypervisor.vmware.util.VmwareClient.waitForValues(VmwareClient.java:428)
        at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:371)
        at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.changeDatastore(VirtualMachineMO.java:344)
        at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4281)
        at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:467)
        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)
Caused by: java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:146)
        at sun.security.ssl.InputRecord.readFully(InputRecord.java:312)
        at sun.security.ssl.InputRecord.read(InputRecord.java:350)
        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:850)
        at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:807) 


- Damodar Reddy


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/16153/#review30091
-----------------------------------------------------------


On Dec. 10, 2013, 11:13 a.m., Damodar Reddy Talakanti wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/16153/
> -----------------------------------------------------------
> 
> (Updated Dec. 10, 2013, 11:13 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek, Likitha Shetty, and Sateesh Chodapuneedi.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-4597
>     https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-4597
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> -------
> 
> When an API command involved with Storage migration and if api command fails then the
complete expection stack trace is getting displayed on the UI.
> 
> 
> Diffs
> -----
> 
>   core/src/com/cloud/agent/api/MigrateWithStorageAnswer.java 6468884 
>   plugins/hypervisors/vmware/src/org/apache/cloudstack/storage/motion/VmwareStorageMotionStrategy.java
5c9b3af 
> 
> Diff: https://reviews.apache.org/r/16153/diff/
> 
> 
> Testing
> -------
> 
> Tested against Live storage migration involved when a VM is migrated to another host
with vmoption not enabled in the back end.
> 
> 
> Thanks,
> 
> Damodar Reddy Talakanti
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message