I am running a .NET web application in its own application pool on IIS7. The parent website is set to run in its own application pool. Today we noticed a huge number of connections going to IIS. I tried to browse a plain ol' .html page in the directory of the web application and it hangs. I then try to browse another plain .html file in the root of the parent website, and it too hangs.
In performance monitor, i see there are some 8k connections to the default website and climbing. I cant seem to understand if my application was the problem, or IIS itself.
If it was my application, wouldnt the html page in the root of the parent website still be able to be served?
edit: Also, if i shut down the app pool to my application, the html page on the root of the parent website is still not able to be displayed.