I was getting timeouts working with VMware API. Most of their commands that can take a long time have an async interface, but some don't, and I was getting frequent timeouts for one of the new commands I started using.
Took me a while to find out the timeout was actually coming from my .net soap proxy and not from the VMware at all.
Seems .net proxies have a client side timeout which is set to 1:40 minutes by default (100,000 msecs). Changing it is just a matter of setting the Timeout property on the proxy.
I still wish VMware would provide an async API for all their long commands, but now at least the problem shifts to making things run concurrently instead of not failing.
just in case I'm not the last person to have to figure this out...
Subscribe to:
Post Comments (Atom)
2 comments:
Thank a lot. You have done excellent job. I enjoyed your blog . Nice efforts
Best facials in Manhattan
Thank you for taking the time to publish this information very useful! responsive wordpress theme
Post a Comment