We have a problem with an asp.net web site that we build and host for clients. Almost a week ago, the website failed to respond to requests only, no error was returned. No code was posted by us but the client periodically uploads non-compiled pages.
Restarting the app pool fixes the problem on the site, but it will be similar in 1-8 hours.
The strange thing is that the IIS log shows that, when the site does not react, the pages are displayed in general, almost as if the request is stuck in a queue or something Are there.
The server's event log does not show anything from the normal This site is running on 2 servers which is balanced with the use of NLB. Switching to one server and showing the same result which indicates that this issue is not environmentally specific, but there is an issue with the application.
We have also run the debug deagag without any obvious consequence. We are not sure about whether there is going to go along with this, whether someone can suggest such a debugging technique. Which can we use to eliminate anything or to discover the source of this issue?
What kind of CPU usage? Is it maximized (possibly app maxed for pool if you set a limit)?
Is it reading from the database? Is it deadlock or otherwise stuck, preventing pages from being loaded?
Comments
Post a Comment