Web Service Shutdown

In a couple of instances, a client can receive an HTTP error 503. When 503 errors are sent out, an event is logged in the Windows Event log. Check the Event Viewer to see whether the error was in HTTP.sys or in the WWW service. If the error is in HTTP.sys, check the application pool queue length. It may be that too many requests have been received. You can modify the application pool queue length manually:

  1. In the IIS MMC, highlight the application pool you want to modify.

  2. Choose Action | Properties, and go to the Performance tab.

  3. Under the Request Queue Limit, increase the value for the number of requests.

  4. Click OK.

If the error message is in the WWW service, it's possible that IIS has detected multiple errors in the worker processes and has initiated the rapid-fail protection. This causes the afflicted application pool to stop serving requests, and it is designed to protect the server from harm by misbehaving applications. If you experience this once, it may be an anomaly. If you experience this multiple times, and frequently, you will want to check out the application configuration, since it appears that something is amiss. You can increase the failure count and time period, but that does not attack the root problem.

Here's how to modify the rapid-fail settings:

  1. In the IIS MMC, highlight the application pool you want to modify.

  2. Choose Action | Properties, and go to the Health tab.

  3. Increase the settings for the failures and/or for the time period that IIS monitors worker process failures.

  4. Click OK.




IIS 6(c) The Complete Reference
IIS 6: The Complete Reference
ISBN: 0072224959
EAN: 2147483647
Year: 2005
Pages: 193

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net