Stopping an Application Pool

  • Article

Applies To: Windows Server 2003, Windows Server 2003 with SP1

Stopping an application pool causes the WWW service to shut down all running worker processes serving that application pool. HTTP.sys is then directed to return HTTP 503-Service Unavailable errors for any requests currently queued for this pool, and to return HTTP 503 errors for all future requests. The application pool is marked as stopped in the metabase and is configured not to start automatically when the WWW service is restarted. You must manually start the application pool to cause it to serve requests again.