Thanks to the blog which explains about the same problem.
Some of the common external dependencies in modern cloud world are: With the above data from MS at least you would be able to know where the problem lies and can review the app again.įor your web apps, you can at least review the code (ensuring it doesn't happen to your azure web apps) where you are handing the connection with external entities. It clearly indicates that Web App 1 worker process is not reusing the connection pool and creating new connections hitting the overall limit of the app service plan. On further request, MS gave us a table of apps under the app service place and their open socket connection count. What? How the heck we know that? As of when i am writing, below were the connection limits given my MS. We opened a case with Microsoft and upon investigation they told us that your App Service Plan (running on Standard S1 2 Instances) are hitting the outbound connection limit. With us, you will get 100mbps all the way to 10gbs with our ultrafast, reliable broadband. IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) +464 It will also limit some applications that use a lot of data regularly. The metered connection should inform you of how much data you are using.
Once set, Windows 10 will remember the settings and keep it as default for further usage. (Boolean connectFailure, Socket s4, Socket s6, Socket& socket, You should change each network separately to metered connection if you want. DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) +208 Few days back I ran into a problem where our production azure web apps were throwing below error: