The VmwareMonitor and the VmwareCimMonitor are able to retrieve the timeout from poller-configuration.xml and pass it to VmwareViJavaAccess (which in turns pass it to com.vmware.vim25.ws.WSClient).

Unfortunately this is not true for VmwareCollector or VMwareCimCollector.

Also, I can't find what's the default timeout used by WSClient when retrieving data from vCenters and/or ESXs.

On big VMWare deployments it is important to set a timeout enough big to be able to complete the transaction and avoid numerous dataCollectionFailed alarms.