mobot
asked on
A process serving application pool exceeded time limits?
We are experiencing problems with application pools and worker processes. The System events point to:
A process serving application pool 'xxxx' exceeded time limits during shut down.
The process id was '<xxxx>'.
Are there suggested settings for properties of the Application Pools like recycling worker processes or memory recycling?
A process serving application pool 'xxxx' exceeded time limits during shut down.
The process id was '<xxxx>'.
Are there suggested settings for properties of the Application Pools like recycling worker processes or memory recycling?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
How do you collect a dump right after recycling?
You can use a tool like Debug Diag from the IIS Diagnostics Toolkit on the Microsoft download site.
Simply make a note of the process ID of the worker process and then generate a full dump of that process from the Processes tab in Debug Diag.
You can then use the Advanced Analysis feature of the tool to try nd get an idea of what the problem is.
Dave Dietz
Simply make a note of the process ID of the worker process and then generate a full dump of that process from the Processes tab in Debug Diag.
You can then use the Advanced Analysis feature of the tool to try nd get an idea of what the problem is.
Dave Dietz
So 'It depends' ;)
What I can tell you is that increasing memory recycling frequency (i.e. the gc) can result in significant performance degradation, as well as early session termination. You need to identify whether your box is underresourced for it's load first (or whether your application design is at fault - e.g. memory leaks)