The information in this article applies to:
SYMPTOMSA computer running Microsoft Internet Information Server (IIS) 4.0 may stop responding to client requests, even though the server appears to be stable and healthy. This situation usually arises from a heavy load; however, IIS does not consume large amounts of CPU or memory resources. This behavior may occur on a per-network interface card, IP address, or TCP port basis. A Network Monitor trace will indicate that the server is immediately resetting TCP connections, indicating that the physical, network, and transport layers are functioning at full capacity. CAUSEThe problem occurs because of a lack of resources at the application layer to handle the requests. RESOLUTIONSet the following metabase parameters: Increasing these values will result in an increase in handle count and memory usage. The values need to be tuned to achieve a balance between load handling capacity and memory usage. MORE INFORMATIONThe ServerListenBacklog property specifies the number of outstanding sockets that can be queued. This value is based on the operating system parameter and the server size specified in the ServerSize property. ServerListenBacklogUse Adsutil.vbs to change the value. The Windows Script Host must be installed on the server to run this Visual Basic script: cscript c:\winnt\system32\inetsrv\adminsamples\adsutil.vbsThe MaxEndpointConnections property specifies the maximum number of listen sockets that will be aggregated on a network endpoint. For example, if this value is set to 15, a maximum of 15 total connections can be made to a single port, even if more than one domain is bound to the port. MaxEndPointConnectionsUse Adsutil.vbs to change the value. REFERENCESOnline Product Documentation Additional query words: Overload time_wait IIS TCP RESETS
Keywords : |
Last Reviewed: September 8, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |