.NET Application Failing - Resolved by Recycling App Pool

Question

I am looking at a .NET ASP application (from the support side - I didn't program it).

It intermittently hangs - the web page doesn't open. Recycling the app pool fixes it.

I can see entries in the event viewer stating

A process server application pool 'wsfrappPool' exceeded time limits during shut down. The process id was '9396' from W3SVC.

I can also see

A worker process with process id of '6804' serving application pool 'AeXRSVaultPool' has requested a recycle because the worker process reached its allowed processing time limit.

I'm looking for advice on how I can track down what is causing the hang and prevent it re-occurring. Can I use performance counters to track this? Are those event viewer entries relevant?

Answer 1

Check the IIS logs to see what the last few requests were before the app went belly up. That may clue you in to what page(s) may be causing the problem.

I had lots of problems like this with .net 1.*, and it was mostly due to out of memory conditions or when the worker process balooned to over 1GB of memory. (There was a lot of large file uploading, a few explicit GC.Collect() calls helped - a bad, but needed fix) Since 2.0, I havent had this kind of problem (large files and all, without the GC.Collects).

• What version of .NET is the page hosted in?
• How many other sites are hosted in the same app pool?

The event viewer events are likely describing your action of recycling the pool.