Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using IISPeek and can see that there's a single request that's hanging on a buggy page. I've fixed the bug so that others who open the page won't experience the problem, but the page is still active after almost an hour.

I'd rather not stop the whole application as there are some important processes currently running.

Via IISPeek I have the request number (9f0002008001238e) and clientIP. Could any of that be used to stop the ongoing request?

share|improve this question

You can't stop an individual request that's hung. You need to recycle the App Pool to do that.

Alternatively, break in with a debugger and terminate the request thread. If the thread's hung, there's no way for it to voluntarily self-terminate.

Keep in mind that when the debugger breaks in, the whole process is paused. And if you don't .detach before quitting, the process will quit, which functionally resembles a recycle anyway.

Extra step: Hope nothing breaks when you do that.

share|improve this answer

Some solution: kill network connection of the server, no need to restart IIS.

share|improve this answer
That's a possibility, but it would still disrupt the currently running important requests. – Petter Brodin May 30 '12 at 10:13

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.