IIS false dead solution: shorten the collection time of IIS application pool to reduce IIS false dead

IIS log:
Application Program : ISAPI 'C: \ windows \ system32 \ inetsrv \ ASP. dll 'reported its own problems because 'asp is abnormal because 100% of the execution request is suspended and 0% of the Request queue is used. '.
About Server 2003 + IIS6, 'asp is abnormal because 100% of the execution request is suspended.
The image is as follows:
The site cannot be opened, or it is slow to open. html can be opened. Restart or recycle application pool can be restored. However, after a while
The log contains:
ISAPI 'C: \ windows \ system32 \ inetsrv \ ASP. DLL 'reported itself as unhealthy for the following reason: 'asp unhealthy because 100% of executing requests are hung and 6% of the Request queue is full. '.
Or:
ISAPI 'C: \ windows \ system32 \ inetsrv \ ASP. dll 'reported its own problems because 'asp is abnormal because 100% of the execution request is suspended and 0% of the Request queue is used. '.
Solution:
1. Is ASP correctly mapped to 'C: \ windows \ system32 \ inetsrv \ ASP. dll'
2. Generally, a site ASP appears in the application pool of the same IIS. Code Errors cause the memory to run out and check the Code itself. You can isolate the code from a separate application pool for debugging.
3. Reduce the collection time of the application pool. 1740 by default .. It can be set to 120 (every 2 hours)
Why IIS is suspended:
Open IIS and you will see the application pool. By default, there is only one application pool. Check the properties of the application pool and you will find that the collection time is up to 1740 minutes by default. That is to say, it takes 1740 minutes to recycle the application pool. If the maximum request limit is reached during this time, ASP will be suspended, this is the case where a large website is suspended for death. On the contrary, this is true for small websites, because they have fewer requests and less traffic, but have not reached the limit. Of course, it depends on the number of websites on your server.
The solution is as follows:
Document 1
Solution for a single website:
The application pool recovery time is shortened to-minutes. During the recovery process, some CPU resources need to be occupied. No way. To ensure stability, set the recovery time to AM.
Solution to multiple websites:
Depending on the number of websites on the server, create multiple application pools and reduce the recycling time of each pool to 300 minutes, then, allocate about 10 Websites in each pool (this allocation requires your website access volume). If a website has a large access volume, assign it a program pool, but the consequence of doing so is that a large memory is needed. A pool now occupies about MB of memory. It doesn't matter if the memory is large anyway,
How to allocate application pools for multiple websites, open IIS, view the website attributes you want to allocate, and view the home directory. Then you can see the application pool. just assign one.
Document 2
When using IIS6 .. if you have installed a dynamic network forum. there must be a false IIS6 image .. ASP Web page opening is slow .. however, IIS is normal .. static web pages are opened at the same speed .. at this time .. I have been restarting .. I checked the official information and found no results... according to official information .. win2003 is about to install this patch soon .. IIS6 does not support access drivers .. it's also a bug .. because my server has many virtual hosts .. and most support ASP .. if it fails to run once it is suspended .. search for various materials .. found a relatively simple method .. I passed the test .. IIS6 comes with a data application pool .. now, we can use it to solve the zombie situation ..
First, set the BBS to a separate directory. Then click the application pool. Create an application pool. Enter the application pool ID ..
Use the application pool under the BBS virtual directory. Select the application pool you just created...
Then return to the application pool we just set up... click .. attribute... check the number of recycling workers (minutes) and the number of recycling workers at the following time .. then add to the left of the recycle pool at the following time .. select a time .. in general .. the website will arrive at a.m. very few people .. at this time, collect the number of BBS processes .. you can solve the problem of false IIS images ..
Of course, you can configure other information .. for example, the IIS6 user name .. we can open the computer management .. then open computer user management .. add a user .. after setting .. in the application pool .. ID .. put the added user .. use the user to test the recycle process .. of course there is .. other configurations .. it's actually quite simple .. just take a look .. you can understand the meaning...
You can also use dedicated tools to recycle application pools .. this is convenient and quick .. IIS backup. uniform modification of the vm ip address and IP record of port access .. batch processing is a simple and convenient method. so. security of a server .. isn't it easy .. especially for IIS .. it is a good habit to search for materials on the official website .. there is also regular access logs .. and the registry user also loads the running program. and services are also a good way.