The process closing time for providing services for the application pool exceeds the limit.

The process shutdown time for the application pool '×××' exceeds the limit. The process ID is '20140901 '.
The ID of the prompt can contain many numbers, such as 3844, 8004, and 6124.
I searched Baidu and found many similar problems. The root cause is unknown, but the direct cause of this situation is IIS failure protection!
For example, if the failure protection is set to fail more than five times every five minutes, the application pool will be closed and the service will be stopped. The prompt log is:
The application pool '×××' is automatically disabled because a series of errors occur in the process that provides services for the application pool.
The solution is as follows:
Internet Information Service (IIS) Manager-> application pool-> defaultapppool-> properties-> running status-> enable quick failure protection!
In order to avoid having to ignore the prompt when many errors are encountered, you can just increase the protection scope of quick protection. For example, if the failure occurs 50 times every five minutes, the corresponding program pool is closed.

 

The closing time of the process that provides services for the application pool 'defaultapppool 'exceeds the limit. The process ID is '20140901 '. For more information, see Help and Support Center in http://go.microsoft.com/fwlink/events.asp.
Note: The ID number is changed. It can be any data such as 3124. Every time this error occurs, the ID is different!
Server performance: iis6.0 false crash, page cannot be opened, ASP page, cannot be executed! Website Cannot be opened

My solution: currently, the IIS server application pool is set as follows:
Right-click the application pool defaultapppool and select properties:
I. Recycling
1. Recycle Working Process (minutes): Selected; Value: 1740
2. Reclaim the Working Process (number of requests): No (originally set to 35000)
3. Reclaim the working process at the following time: do not fill in
4. Process recycling when too much memory is consumed: all are not selected. (Items 2, 3, and 4 may avoid server response problems that may be caused by the forced recycle process when the traffic is high. You can guess the ^-^) The server memory is large enough to be used out.
Ii. Performance
Only idle timeout for 20 minutes is selected. None of them. The maximum number of worker processes in the Web garden is 1 (default ). The original request queue is limited to 4000, But not limited now.
Iii. Running status
The first two items are used by default. The startup time is limited to 90 seconds, and the shutdown time is limited to 180 seconds.

The "Closing time limit is 180 seconds" is required because the process closing time is set here. It is originally set to 90 seconds, which is the default value. If the closing time of a process exceeds 90 seconds, it is deemed to have timed out, and thus the process shutdown time exceeds the limit log. Therefore, extend the time appropriately to avoid this error!

The closing time of the process that provides services for the application pool defaultapppool exceeds the limit.
The server frequently generates the "application pool" defaultapppool "to provide services. The process shutdown time exceeds the limit. The process ID is 2068 ″." The IIS is in the suspended state. It is known that it is a problem in setting the IIS application pool. The solution is as follows:

Internet Information Service (IIS) Manager-> application pool-> defaultapppool-> right-click Properties
I. Recycling
1. Recycle Working Process (minutes): Selected; Value: 1740
2. Reclaim the Working Process (number of requests): No (originally set to 35000)
3. Reclaim the working process at the following time: do not fill in
4. Process recycling when too much memory is consumed: all are not selected. (Items 2, 3, and 4 may avoid server response problems that may be caused by the forced recycle process when the traffic is high, leading to false IIS response failure)
Ii. Performance
Only idle timeout for 20 minutes is selected. None of them. The maximum number of worker processes in the Web garden is 1 (default ). Note that the Web Garden must be kept by default. If you enter other numbers greater than 1, the background programs of some website programs cannot be opened or refresh continuously.

The original request queue is limited to 4000, But not limited now.
Iii. Running status
The first two items are used by default. The startup time is limited to 90 seconds, and the shutdown time is limited to 180 seconds.

Remove the hook for enabling the quick failure protection!
In order to avoid having to ignore the prompt when many errors are encountered, you can just increase the protection scope of quick protection. For example, if the failure occurs for 50 times for five minutes, you can close the corresponding program.

The "Closing time limit is 180 seconds" is required. Because the process closing time is originally 90 seconds, it is the default value. If the closing time of a process exceeds 90 seconds, it is deemed to have timed out, this error occurs when the process shutdown time exceeds the limit log. Therefore, extend the time to avoid this error.

2nd methods:

Cause: the memory heap quota of independent processes is exhausted, and IIS cannot create more process workspaces for processing.

Solution:
1. HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ W3SVC
2. Create a New DWORD under the Parameters key. The name is usesharedwpdesktop and the value is 1. Restart IIS.

3rd types

The problem has been solved and the database connection cannot be released. I don't know why. The same code is good locally and there is a problem on the server, finally, add the following statement to the connection string to solve the problem.

Pooling = true; Max pool size = 512; min pool size = 50; connection lifetime = 30

4th types

Create an application pool. different websites reference different application pools.