We most likely have a memory leak in our asp application, but it may be some time before we can effectively address this problem.
Every so often, our website hangs and shows a page stating their is an outofmemory exception.
The problem is that IIS does not restart the worker process because it is responding to the health pings. It's not completely crashed which is how it's basically described in MS KB.
If the worker process completely died, it would be restarted because there would be no response to a ping.
What we need, is a way to detect when the web server is showing an outofmemoryexception to the website visitor, and recyle the affected worker process(we have two) all automatically of course.