[
https://issues.apache.org/jira/browse/CLOUDSTACK-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834511#comment-13834511
]
Likitha Shetty commented on CLOUDSTACK-5069:
--------------------------------------------
Steve, i am not sure if it can be merged to 4.2.1. The release manager for
4.2.1, Abhinandan Prateek should be able to make that call.
About the source where the value has been hardcoded ,it is in file
_vmware-base/src/com/cloud/hypervisor/vmware/util/VmwareClient.java_
ctxt.put("com.sun.xml.internal.ws.request.timeout", 1200000);
ctxt.put("com.sun.xml.internal.ws.connect.timeout", 1200000);
> Make VMware vCenter session timeout value configurable.
> -------------------------------------------------------
>
> Key: CLOUDSTACK-5069
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5069
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Priority: Critical
> Fix For: 4.3.0
>
>
> We see socket timeout errors in a VMware setup if a VMware task
> (RelocateVM_Task, CloneVM_Task etc.) takes more than 20 minutes.
> Add a global config 'vmware.vcenter.session.timeout' to make the vCenter
> session timeout value configurable.
> Note that VMware tasks like CloneVM_Task take longer if we use the default
> full-clone mode and a slow storage.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
