Geek asks and answers

IIS served ASP.NET applications after maintenance about 5-10 times

I serve the application through IIS 8.0 under Windows 8. The site consists of static html and js files that use ASP.NET Web.Api 2 and SignalR to communicate with the server.

Pages load very quickly and work fine until I open several instances in ~ 5-10 tabs, and then everything stops. Chrome either shows "waiting for a hostname" or "waiting for an available socket."

If I have 4 pages loaded, and it freezes, trying to load another 1, I can just close the other tabs, and the latter will load after a while.

My question is, how can I debug this problem, what tools are available to help me find out where the hang is?

+3
source share
1 answer

When IIS starts on Windows 8, there is a limit on the simultaneous request, the connection attempt is on the Windows server, and you will not have problems with several concurrent requests.

(Cut from the following article for future reference)

Windows 8 - IIS 8 simultaneous request limitation

Windows 8 (Basic Edition) 3
Windows 8 Professional, Enterprise 10

IIS Parallel Query Limitations for Different Versions of Windows

+5
source

More articles:


All Articles