ProcessModelSection.RequestQueueLimit Property

public:
 property int RequestQueueLimit { int get(); void set(int value); };

[System.ComponentModel.TypeConverter(typeof(System.Configuration.InfiniteIntConverter))]
[System.Configuration.ConfigurationProperty("requestQueueLimit", DefaultValue=5000)]
[System.Configuration.IntegerValidator(MinValue=0)]
public int RequestQueueLimit { get; set; }

[<System.ComponentModel.TypeConverter(typeof(System.Configuration.InfiniteIntConverter))>]
[<System.Configuration.ConfigurationProperty("requestQueueLimit", DefaultValue=5000)>]
[<System.Configuration.IntegerValidator(MinValue=0)>]
member this.RequestQueueLimit : int with get, set

Public Property RequestQueueLimit As Integer

Property Value

The number of requests allowed to be queued. The default is 5000.

Attributes

TypeConverterAttribute ConfigurationPropertyAttribute IntegerValidatorAttribute

Examples

The following code example shows how to use the RequestQueueLimit property.

// Get the current RequestQueueLimit property value.
int requestQueueLimit =
    processModelSection.RequestQueueLimit;

// Set the RequestQueueLimit property to 10240.
processModelSection.RequestQueueLimit = 10240;

' Get the current RequestQueueLimit property value.
   Dim requestQueueLimit As Integer = _
   processModelSection.RequestQueueLimit

' Set the RequestQueueLimit property to 10240.
processModelSection.RequestQueueLimit = 10240

Remarks

If the number of requests allowed in the queue is exceeded, ASP.NET begins returning "503 - Server Too Busy" errors to new requests. When this limit is reached, the system is operating in abnormal conditions. This might be a symptom of a malfunction or, maybe, just high load. Restarting (bouncing) the worker process might become the only way to prevent further problems.

Applies to