About WIN2003 IIS6.0 no problem to stop

This problem has plagued me for half a month. A server running WIN2003 IIS6.0. Occasionally. ASP can not access. But in the meantime. CGI PHP HTM JSP everything is normal. After many trials. Solve the problem as follows .

Open IIS and you will see the application pool. The default is only one application pool. You can view the properties of the application pool. You will find his recycle time. The default is up to .1740 minutes. That is to say. It takes about 1740 minutes to reclaim this application pool. If the maximum limit of the request is reached within this time, then ASP will be suspended. This is the case of a large website with a suspended animation. Instead, the small website does not appear. This situation. Because he requests less. The traffic is less. The number has not yet reached the limit.

Less talk. How to solve?;

Of course, depends on how many websites your server has pulled up. The following is my solution.

Single website solution.;

(very simple. Reduce the application pool recovery time to 300-600 minutes. During the recycling process. Need to take up a little CPU resources. No way. For stability Then set the recycling time to 5 am)

Multi-site solution.

My server is currently pulling about 70 websites. I am creating six new application pools. Put each The pool collection time is reduced to 300 minutes. Then allocate about 10 websites per pool (this allocation is required by your website traffic). If a website has a large amount of traffic, give him a program pool separately. But do this. The consequence is that it requires a lot of memory. A pool now takes up about 120M of memory. Anyway, the memory is big. It doesn't matter.}'
How do multiple websites allocate application pools?? Open IIS--View the website attributes you want to assign.. Look at the main directory - below you will see the application pool. Assign one on the line.

The above is my clinical trial. The server is now running stably. It has been stopped almost once a day. I restarted IIS
Computer hardware and software application website long note: This situation generally only appears in IIS6.0, because only IIS6.0 uses this design. Generally reducing the recovery time can alleviate this situation! Sometimes it is also due to the fake operation of the website itself! If the above method can not be completely solved, it is recommended to turn off the error protection function to try!