4

I have an IIS 6 server serving an application using a mix of classic ASP and ASP.NET.

I'm increasingly getting problems where the number of requests in the ASP.NET requests queue (observed using the ASP.NET\Requests Queued counter) starts to increase to a point where the server can no longer service the requests. That happens a three or four minutes from the point where queued requests starts increasing. Recycling the application pool restores service.

Normally, requests queued is zero and occasionally there'll be small spikes but it seems that once or twice a day, a number of requests are blocking the queue and queued requests starts to increase.

I suspect there are network problems causing clients to lose their connection (and re-submit their request) and the requests in the queue continue despite losing their client.

How can I diagnose the problem? Can I look at the status of requests in the queue? Do I need the MS Debug Diagnostic Tool or one of these tools?

Improve this question
2
  • Do you know how many requests/sec you're servicing before this starts happening?
    – Joseph
    Apr 30, 2009 at 17:17
  • A maximum of 6 requests/sec, averaging around 1 request/sec (from the ASP.NET Applications(Total)\Requests/Sec counter)
    – Robin M
    May 1, 2009 at 13:55

2 Answers 2

Reset to default
2

I've discovered that the MS Trace Diagnostics tool (IISReqMon) from this list of "Useful tools and add-ons for IIS troubleshooting and IIS7" will give me information about the current worker processes and their requests in an application pool.

Improve this answer
0

Not much help in debugging, but I would suspect a deadlock in code rather than network as IIS is pretty well debugged as far as connectivity. I would not expect it to fail like that.

I'm guessing your site has got busier of late, hence the deadlock issues.

Improve this answer
0

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .