Event ID 5074 — IIS Application Pool Recycling

Updated: January 20, 2010

Applies To: Windows Server 2008

Internet Information Services (IIS) application pools can be periodically recycled to avoid unstable states that can lead to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means that the worker process that is to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients. However, if an application in the application pool cannot run more than one instance of itself at a time, overlapping rotation can be disabled.

Event Details

Product:

Internet Information Services

ID:

5074

Source:

Microsoft-Windows-WAS

Version:

7.0

Symbolic Name:

WAS_EVENT_RECYCLE_WP_TIME

Message:

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

Resolve

Check or configure application pool limits

A worker process requests a recycle when it reaches its configured limits for time, number of requests, or memory usage. An underlying issue may have caused the configured limit to be reached. You can check or configure the application pool limits by using IIS Manager.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To check or configure application pool limit settings by using IIS Manager:

Click Start, click Control Panel, and then click Administrative Tools.