I've been tracking (or trying to track) why my ASP applications occasionally lose their sessions. It never occurs at the same time. Yesterday, I was at my desk when it happened, so I checked out the event logs on the server, and found this event.
I am not familiar with application pool design, but if I'm reading the error right, I think there's a page in one of the web apps that fall under this pool that is taking an exceptional amount of time to finish. I have about eight different web apps using this application pool, so I'm not sure who the culprit is.
I'm looking over some other questions here to get a better understanding of IIS Application Pools, and believe I do have some work to do to get my pools operating better.
- IIS 7.x Application Pool Best Practices
- IIS7.5 App Pool recycling. What is the best schedule for Recycling
- IIS 7.5, need help to understand how app pool recycling works
However, even if the pools are reworked some, I still fear I have a page that is exceeding the "allowed processing time limit". Before I increase the limit, is there a way to see the name of the page that is exceeding the "allowed processing time limit", resulting in the recycle?
