You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Damodar Reddy Talakanti <da...@citrix.com> on 2013/12/10 12:13:57 UTC
Review Request 16153: Fixing by chanding the constructor of
MigrateWithStorageAnswer not to include stack trace in the details.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/16153/
-----------------------------------------------------------
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
Re: Review Request 16153: Fixing by chanding the constructor of
MigrateWithStorageAnswer not to include stack trace in the details.
Posted by Damodar Reddy Talakanti <da...@citrix.com>.
> 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
>
>
Re: Review Request 16153: Fixing by chanding the constructor of
MigrateWithStorageAnswer not to include stack trace in the details.
Posted by Damodar Reddy Talakanti <da...@citrix.com>.
> 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?
>
> Damodar Reddy Talakanti wrote:
>
> 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)
>
> Sateesh Chodapuneedi wrote:
> Hi,
> I am looking for the exception messages observed in testing this patch. Would like to see them against the messages in the reported bug.
> Thanks.
This is what I have seen in the UI (Another trace below this is present in the logs)
com.cloud.utils.exception.CloudRuntimeException: Failed to migrated vm VM[User|d-5054] along with its volumes. Error while migrating the vm VM[User|d-5054] to host Host[-1-Routing]. The vMotion interface is not configured (or is misconfigured) on the Source host '10.147.28.15'.
at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.migrateVolumes(VolumeOrchestrator.java:908)
at com.cloud.vm.VirtualMachineManagerImpl.orchestrateMigrateWithStorage(VirtualMachineManagerImpl.java:1945)
at com.cloud.vm.VirtualMachineManagerImpl.migrateWithStorage(VirtualMachineManagerImpl.java:1872)
at com.cloud.vm.UserVmManagerImpl.migrateVirtualMachineWithVolume(UserVmManagerImpl.java:4518)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy176.migrateVirtualMachineWithVolume(Unknown Source)
at org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd.execute(MigrateVirtualMachineWithVolumeCmd.java:138)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:520)
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
This is present in the logs...
2013-12-10 16:23:19,474 ERROR [o.a.c.s.m.VmwareStorageMotionStrategy] (Job-Executor-1:ctx-14a9458b ctx-06abc156) copy failed
com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm VM[User|d-5054] to host Host[-1-Routing]. The vMotion interface is not configured (or is misconfigured) on the Source host '10.147.28.15'.
at org.apache.cloudstack.storage.motion.VmwareStorageMotionStrategy.migrateVmWithVolumesAcrossCluster(VmwareStorageMotionStrategy.java:142)
at org.apache.cloudstack.storage.motion.VmwareStorageMotionStrategy.copyAsync(VmwareStorageMotionStrategy.java:101)
at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:89)
at org.apache.cloudstack.storage.volume.VolumeServiceImpl.migrateVolumes(VolumeServiceImpl.java:988)
at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.migrateVolumes(VolumeOrchestrator.java:903)
at com.cloud.vm.VirtualMachineManagerImpl.orchestrateMigrateWithStorage(VirtualMachineManagerImpl.java:1945)
at com.cloud.vm.VirtualMachineManagerImpl.migrateWithStorage(VirtualMachineManagerImpl.java:1872)
at com.cloud.vm.UserVmManagerImpl.migrateVirtualMachineWithVolume(UserVmManagerImpl.java:4518)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy176.migrateVirtualMachineWithVolume(Unknown Source)
at org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd.execute(MigrateVirtualMachineWithVolumeCmd.java:138)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:520)
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
- 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
>
>
Re: Review Request 16153: Fixing by chanding the constructor of
MigrateWithStorageAnswer not to include stack trace in the details.
Posted by Sateesh Chodapuneedi <sa...@citrix.com>.
> 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?
>
> Damodar Reddy Talakanti wrote:
>
> 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)
Hi,
I am looking for the exception messages observed in testing this patch. Would like to see them against the messages in the reported bug.
Thanks.
- Sateesh
-----------------------------------------------------------
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
>
>
Re: Review Request 16153: Fixing by chanding the constructor of
MigrateWithStorageAnswer not to include stack trace in the details.
Posted by Sateesh Chodapuneedi <sa...@citrix.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/16153/#review30091
-----------------------------------------------------------
Can you please share the exception messages observed in testing against exception messages printed in web UI earlier?
- Sateesh Chodapuneedi
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
>
>