In IIS 6 it is possible to assign more than one worker process to an App pool (known as a Web Garden). This is a nice way to increase performance, but it will make your application act randomly if the asp.net cache is used. This is because you will actually be connecting to different instances of the application which may or may not have had their cache updated when a change has been made.
The best way to correct this erratic behavior is to make sure that you are not running in a Web Garden. To do that, you need to use the IIS manager and set the properties of the application pool your application is running under to use only one worker process.
1.
In IIS Manager, expand the local computer, expand Application Pools, right-click the application pool, and then click Properties.
2.
Click the Performance tab, and under Web garden, in the Maximum number of worker processes box, type the number of worker processes that you want to assign to the application pool. (You must type a number greater than 1 for the application pool to become a Web garden.
3.
Click OK.
Optionally, you can configure a Web garden by setting the metabase property MaxProcesses. The MaxProcesses property determines the maximum number of worker processes that an application pool allows to service its requests. A value of zero indicates an unmanaged application pool that is not served by a worker process.
The default value for the MaxProcesses property is 1, which is the default number of worker processes that service an application pool. To configure an application pool so that it is not a Web garden, set the MaxProcesses property to back to 1.
Remember Me
