DisableSocketPooling

The DisableSocketPooling property specifies whether socket pooling is used for sites distinguished by IP address, rather than port number or host header name. If DisableSocketPooling is set to false, socket pooling is enabled and sockets are shared between sites that use the same port number (but different IP addresses). If DisableSocketPooling is set to true, there is no socket sharing for sites based on IP address.

By default, socket pooling is enabled. In general, this behavior should not be modified. If changed, the change should be made at the site level only so that other sites can continue to take advantage of the socket pooling feature.

IIS 6.0: Socket pooling was first introduced in IIS 5.0. Because DisableSocketPooling is defined as a valid property in the IIS 6.0 metabase schema (MBSchema.xml), you can still set this property, but the setting has no effect. In IIS 6.0, the HTTP listener is in the new kernel-level driver, HTTP.sys. To configure HTTP.sys, you must modify an IP inclusion list using Httpcfg.exe. For more information, see article Q813368, "IIS 6.0: Setting Metabase Property DisableSocketPooling Has No Effect," in the Microsoft Knowledge Base at https://support.microsoft.com.

IIS 4.0: In IIS version 4.0, each Web site was bound to a different IP address, which meant that each site had its own socket that was not shared with sites bound to other IP addresses. These sockets are created when the site starts, and they consume significant nonpaged memory (RAM). This memory consumption limits the number of sites bound to IP addresses that can be created on a single computer.

Schema Attributes

Configurable Locations

You can configure this property at the following locations in the IIS metabase.

Flags

There are no flags for this property.

Requirements

Client: Requires Windows XP Professional, or Windows 2000 Professional.

Server: Requires or Windows 2000 Server.

Product: IIS

See Also