AspQueueConnectionTestTime
IIS places all ASP requests into a queue. If the request has been queued for longer than the number of seconds specified by AspQueueConnectionTestTime, ASP checks to determine whether the client is still connected before executing the request. If the client is no longer connected, the request is not processed and is deleted from the queue.
.gif)
Note Users often will not wait very long for ASP pages to process. Although the maximum waiting time varies from user to user, the generally accepted maximum is approximately 10 seconds. You can use the AspQueueConnectionTestTime property to ensure that IIS does not waste time processing a request that has been abandoned by the user. This property is useful for making ASP processing efficient only up to the point at which ASP begins to process the script. Once the script is running, however, your application should continue to check for client connection at appropriate times, by using the IsClientConnected method of the ASP built-in Response object.
| Attribute Name | Attribute Value |
|---|---|
| XML Data Type | DWORD |
| WMI Data Type |
SINT32
|
| ADSI Data Type | DWORD |
| ABO Data Type | DWORD |
| ABO Metabase identifier |
MD_ASP_QUEUECONNECTIONTESTTIME
|
| Attributes | INHERIT |
| Default Value | 3 |
| MetaFlagsEx | CACHE_PROPERTY_MODIFIED |
| User Type | ASP_MD_UT_APP |
| StartingNumber | Not applicable |
| EndingNumber | 0 |
| ID | 7028 |
Configurable Locations
You can configure this property at the following locations in the IIS metabase.
| Metabase Path | IIS Admin Object Type |
|---|---|
| /LM/W3SVC/n/ROOT /LM/W3SVC/n/ROOT/virtual_directory_name |
IIsWebVirtualDir |
| /LM/W3SVC/n | IIsWebServer |
| /LM/W3SVC | IIsWebService |
| /LM/W3SVC/n/ROOT/physical_directory_name /LM/W3SVC/n/virtual_directory_name/physical_directory_name |
IIsWebDirectory |
Code Example
For general code examples, please see Code Examples to Configure Metabase Properties