Consultor Eletrônico

Status: Verified

GOAL:

What are IIS 6.0 Application Pools

GOAL:

How to Create IIS 6.0 Application Pools

GOAL:

What are Worker Processes in IIS 6.0 Application Pools

GOAL:

How to assign a Web Site to an Application Pool

GOAL:

How to Configure an Application Pool in IIS 6.0

FACT(s) (Environment):

Windows
IIS 6.0
IIS 6.1

FIX:

An application pool provides a way of isolating Web sites from each other even though they are being hosted on a common server. Each application pool is given its own set of server resources. That way, if a Web site crashes, it will not affect sites in other application pools. A classic example of this is a Web site with a memory leak. If all of the Web sites hosted on a particular server were to share system resources, and one of the Web sites had a memory leak, it could potentially take memory away from the other hosted sites. If the leaky site were in its own application pool though, the memory leak would not affect any other site because each application pool has its own server resources (including memory).
Although IIS 6 allows you to use application pools, there is only one application pool by default. As you create new Web sites on the server, the newly created sites are lumped into the default application pool unless you tell IIS to do otherwise. IIS will not automatically create a separate application pool for each Web site.
In the sections that follow, there are references to worker processes. A worker process is simply a process that actually runs the Web site. Each application pool has one or more worker processes. The worker processes are unique to the application pool and are not shared across application pools.

Creating a New Application Pool
To create an application pool, open the Internet Information Services (IIS) Manager, right click on the Application Pools container, and select the New | Application Pool commands from the shortcut menus.
A dialog box is displayed that asks for a name for the new application poo. E