In IIS 7, you can view the worker processes and see which requests are currently executing. I am encountering some requests that remain in the "ExecuteRequestHandler" stage for hours - basically until the application pool is recycled. I am unsure why this is happening but it appears to correlate with "connection_dropped" errors in the httperr.log file.
I want to ensure these requests aren't tying up resources (we're seeing memory spikes as well, though I can't necessarily tie the two together; CPU for the requests is 0%), so is there a way to limit the amount of time a request can have? I found one for classic ASP but nothing for .NET.