You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default timeouts for winhttp are not large enough for some operations.
For example, when reading from service bus, it is possible to give azure a timeout to wait for availability of a message in the queue (let's say 40 secs). If that timeout is larger than the winhttp timeout (30 secs), you'll get a timeout error from winhttp after 30 secs.
There is a limitation of 60 secs for any Azure calls through http:
"When using http, the load balancer will kill any connection after a minute of inactivity. "
So we can probably just set the timeouts to 60-70 secs.
The text was updated successfully, but these errors were encountered:
The default timeouts for winhttp are not large enough for some operations.
For example, when reading from service bus, it is possible to give azure a timeout to wait for availability of a message in the queue (let's say 40 secs). If that timeout is larger than the winhttp timeout (30 secs), you'll get a timeout error from winhttp after 30 secs.
There is a limitation of 60 secs for any Azure calls through http:
"When using http, the load balancer will kill any connection after a minute of inactivity. "
So we can probably just set the timeouts to 60-70 secs.
The text was updated successfully, but these errors were encountered: