Share via

AspSessionMax

  • Article

AspSessionMax specifies the maximum number of concurrent sessions that IIS will permit. If a client attempts to establish a new session with IIS once this limit is reached, the client will receive an error (HTTP 500 "Server Too Busy").

note Note ASP incurs a certain amount of memory overhead for each session maintained. Although you could use AspSessionMax to limit this memory overhead, it is generally more appropriate to manage the lifetime of session objects within IIS by using the AspSessionTimeout property, so that client browsers will be rejected once the limit is reached.

If an incoming request does not have an ASP session cookie, or has a session cookie that does not match an existing session,the incomingrequestis considered a new session request. The Web service setting for this property is applicable to all in-process and pooled out-of-process application keys, at all levels. Metabase settings at the Web server level or lower will be ignored for in-process and pooled out-of-process applications. However, settings at the Web server level or lower will be used if thatkey is an isolated out-of-process application.

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_SESSIONMAX
Attributes INHERIT
Default Value 4294967295
MetaFlagsEx CACHE_PROPERTY_MODIFIED
User Type ASP_MD_UT_APP
StartingNumber Not applicable
EndingNumber 0
ID 7029

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

AspSessionTimeout