I have an ASP.NET application that uses both an HTTPModule and several HTTPHandlers. This application is running in a web farm environment on Windows 2003 Server using NLB. Under somewhat heavy load (~25 req/sec) the application begins to return HTTP 404 errors
for requests of a specific handler. The other handlers continue to work fine. This usually happens after about 30 minutes of sustained load. I don't think it is something in my code because I use this same code (or, rather, very, very similar code) in several
other applications - including applications that handle close to 300 req/sec. I could, of course, be wrong. Whatever the issue, it appears to be cumulative. Over the course of several hours, eventually all machines in the server farm will start returning nothing
but 404's for that handler. In addition, once a machine has returned a 404 for the handler, it always returns a 404. If I recycle the app domain, or if I change the web.config or replace the DLL, the application begins to work again. Could it be that some
querystring being passed to the handler is causing it to fail, then permenantly bringing down the handler from that point on? Any ideas?
Is there anyway that your handler could be looping internally. I know that we have an errorhandler that starts looping if our custom error page throws an error. I haven't let it run, but I could imagine it eventually locking up the handler...
Member
10 Points
171 Posts
HTTPHandler 404 Under Heavy Load
Jun 30, 2004 11:48 AM|RMD|LINK
Contributor
3294 Points
3302 Posts
Re: HTTPHandler 404 Under Heavy Load
Jun 30, 2004 10:33 PM|stiletto|LINK
Member
10 Points
171 Posts
Re: HTTPHandler 404 Under Heavy Load
Jul 01, 2004 05:14 PM|RMD|LINK