On vCAC 5.2 I am experiencing that workflows against my vCenter server are queued up until I restart my vSphere agent.
Apparently, the agent lost connection to the vCenter server's SOAP service and does not try to reconnect without the restart.
In it's fluke state, the agent looks healthy to the rest of the vCAC services and continues producing ping reports for esx clusters.
I have experienced two causes for disconnections: windows updates on the agent's host and downtime on the vCenter server.
No events or log records have been found yet from the agent's problems with the vCenter SOAP service.
The question: is there anything I can configure on the vsphere agent to improve this situation?
