Debug TCP / IP port exhaustion in Azure WebApp

Question

I get a TCP / IP port exhaustion error in a web application deployed to Azure App Services. The problem is with a RavenDB connection session that has ports. I think I have a fix and should be fine, but I feel superior because I really could not do much to debug in a deployed environment.

In debugging the problem, I tried to access netstat, but I got access to the failure message and cannot get around it. Any suggestions?

On the tangent: how are ports allocated in Azure webapp? The parameters specified in https://msdn.microsoft.com/en-us/library/aa560610(v=bts.20).aspx ), it is necessary to reduce the value of the socket connection timeout or increase the upper range of ports dynamically allocated to client TCP / IP. However, I do not think this is possible in Azure Web Apps.

Answer 1

This could be solved by updating the Ravendb instance! More details here: https://ayende.com/blog/173057/production-postmorterm-houston-we-have-a-problem .

From the changelog version 3.0.30100 :

​​ UDP

, 3.0.30115:

[Major] [Prefetching] ​​ , ,

Azure : http://www.freekpaans.nl/2015/08/starving-outgoing-connections-on-windows-azure-web-sites/

, async, UDP /. , async, , , , iisreset.

, 24 , , , , .

, , - - Ravendb .