Article ID: 816995 - View products that this article applies to.
The Internet Information Services (IIS) 6.0 documentation states that the AppPoolQueueLength property indicates to HTTP.sys how many requests to queue in an application pool before returning the following error message:
Note In the Httperr.log file, you will see error code 503 along with the message "QueueFull". The browser only displays the message "Service Unavailable".
HTTP 503: Service Unavailable
In implementation, however, the property does not behave as described in the IIS 6.0 core documentation.
Note In Internet Information Services 7.0, the AppPoolQueueLength size has been renamed as QueueLength. QueueLength has a default value of 1,000 and is configurable in the Application Pool section of Internet Services Manager.
The AppPoolQueueLength property controls how many total requests are permitted for the application pool. These include any requests already in user mode, requests that are being processed, and requests that are still queued in the kernel mode HTTP.sys listener.
The default value for this property is 4000 total requests (user and kernel mode requests). The total count of requests for an application pool is only decremented when a request has been completely served. If long-running requests occur in applications, the default of 4000 requests may not be adequate.
To set AppPoolQueueLength to a higher value (for example, to 4500), use one of the following two methods:
Note When you change this value, Microsoft recommends that you test the new value thoroughly because this increase may cause the application to perform poorly because of the additional resources being used by the queuing.