The Data Service detected slow execution -VMware vSphere Webclient reports data query service time out.

Error:

virgo.log reports ,

“com.vmware.vise.data.query.DataServiceException: The data service timed out because a back-end task took more than 120 seconds. See the vsphere-client-virgo.log for more details.”

vSphere_client-Virgo.log reports below error:

 The Data Service detected slow execution:A DataProviderAdapter execution took too long: xxxx milliseconds.

Symptoms:

• vSphere web client takes longer time than usual for loading after logging in.
• vSphere web client may report “Data query service Timed out”
• Restarting VMware webclient service may not fix the issue.

Cause:

VMware webclient uses data query service to fetch information from all dependent services of the plugins installed in the machine. All vSphere plugins like SRM , vRealize operations etc .. and third party plugins will communicate to the vSphere web client through this service.

Whenever the data query service is taking longer time to fetch larger workflow information from vRealize or any other plugins , this error is popped up in web client.

Some of the possible reasons are ,

• Stale vCenter server object linked to this vCenter in linked mode.
• Any VSM plugin installed while VSM was already decommissioned.
• vRealize operations automated larger workflows at the same time.

Temporary Workaround:

• Restarting the machine where VMware Webclient is installed would fix the issue temporarily.

Permanent Fix:

Firstly, find out which plugin is the culprit to resolve the issue. To find it , open the virgo-server.log ,

Locate for below messages,

java.lang.NullPointerException: null
at  Plugin_Name.ObjectNavigatorVSphereDataAdapter.processQuery(ObjectNavigatorVSphereDataAdapter.java:228)
at Plugin_Name.ObjectNavigatorVSphereDataAdapter.getData(ObjectNavigatorVSphereDataAdapter.java:206)
at com.vmware.vise.data.query.impl.DataAdapterUtil.getDataFromAdapter(DataAdapterUtil.java:127)

Plugin_Name is the plugin which is causing the issue.

• If that is because of your vRealize operations manager plugin , the read.timeout value can be modified as described in  VMware KB.

• To remove an orphaned VSM plugin , follow the KB article from Cisco.

• If you have a stale vCenter linked , Please run the below command to unregister the vCenter that was decommissioned.

            cmsso-util unregister –node-pnid vCenter-Server-System-Name –username                     administrator@vsphere.local  –passwd vCenter-Single-Sign-On-password