Strange problems encountered by the blog program in the blog Park

Blog of the blog Park Program After being upgraded to ASP. NET 2.0, it has been plagued by the following problems:
When a problem occurs, from the client, the browser is in the connection status, but the server's response is never received. From the server perspective, the CPU usage is very low, not more than 10%. My understanding of this phenomenon is that IIS receives the request and forwards it to the ASP. NET 2.0 process for processing, while the ASP. NET 2.0 process is not working and does not respond to the request.
The application pool of IIS 6 checks the health status of the worker process every 30 seconds (the default setting) and discovers ASP. NET 2.0 process, immediately shut down the process, establish an innovative process, the new process is busy for a while, the system returns to normal.
Event Log information:
System log (event ID: 1010 ):
A process serving application pool 'app _ cnblogs' failed to respond to a ping. The process ID was '123 '.
Note: This is the information recorded when the application pool checks the health status of the worker process.
The occurrence of this problem is not regular. The number of times is not fixed. When the traffic volume is large, more times occur. After updating the DLL file, the probability of occurrence is high.
This kind of non-working status is caused by a deadlock in program execution, or ASP. NET 2.0 engine found an exception and actively exited the operation. asp. NET 2.0 has this feature, and Microsoft's documentation says that if. if an unhandled exception occurs while the NET 2.0 program is running, the program will exit. I have handled this problem according to Microsoft's documentation, and the problem still exists. I found that even if an unhandled exception occurs, the program will not exit as described in the document. ASP. NET 2.0 will log the exception into the event log and the program will run as usual.
So far, I have not found the cause of the problem. When the problem occurs, Asp. NET 2.0 runtime does not record some relevant information in the event log, I did not expect any way to capture more information when the problem occurs, in the program did not find the cause of the Process deadlock Code .
Is it a blog garden program bug or an ASP. NET 2.0 bug? I have not found any clue about the problem. I wrote it today. I want to know if any of my friends has encountered this problem, and I hope some experienced friends can provide some suggestions.
Related Article : Why does the application pool always crash (crash)