IIS application pool frequently crashes

1. The error log file is as follows:

Note: The file is located in the C: \ WINDOWS \ system32 \ LogFiles \ HTTPERR directory.

In addition, IIS also has a log, which is specified in the Properties window below.

 

 

 

 

After analysis, this error log mainly contains three types of errors

 

• 10:43:27 203.208.60.20.48675 210.192.111.49 80 HTTP/1.1 GET/showroom/vulpes/product-detail/LRPST/Rubber-Series-2006987705 export MyApplicationPool: this error indicates that the connection is forcibly dropped.
• 11:25:50 211.167.234.158 13284 210.192.111.49 80--Timer_ConnectionIdle-
• 10:53:05 211.139.116.67 27664 210.192.111.49 80---Timer_MinBytesPerSecond-these two errors are time-related.

 

 

2. analyze the cause of the Error

For Timer_ConnectionIdle and Timer_MinBytesPerSecond, consider the following measures:

This error occurs in IIS6.0 system logs: Timer_MinBytesPerSecond, Timer_ConnectionIdle

Description: The Error means The connection with the server has been terminated.

Problem description: this error is caused by server connection interruption.

If you check out the C: "Windows" system32 "LogFiles" HTTPERR "httperr *. log files on the distribution server, you'll likely see either Timer_MinBytesPerSecond errors or Timer_ConnectionIdle errors. these are caused by IIS 'default settings, contained within its metabase, which define the minimum traffic flow rate for a connection to be kept alive and the maximum idle time allowed before a connection is dropped. for some reason, SUS servers seem to take their good old time while downloading updates, and these parameters are exceeded and the distribution server drops 'em.

This problem is caused by improper default settings of IIS in some applications.

1) From IIS Manager, right click on the Internet Information Server (IIS) Manager root level folder and go to Properties. Check the box to enable direct metabase editing. Click OK.

1) Open the Internet Information Service (IIS) manager, right-click "my computer"-properties, and select "allow directly edit configuration database (N)". OK.

2) Open the C: \ Windows \ system32 \ inetsrv \ MetaBase. xml file in Notepad. do a search for "MinFileBytesPerSec ". change the setting for MinFileBytesPerSec from 240 to 0. do another search, this time for "ConnectionTimeout" to be 600. save changes and exit.

2) edit the C: "Windows" system32 "inetsrv" MetaBase. xml file, change the value of MinFileBytesPerSec from 240 to 0, and set ConnectionTimeout to 600.

3) Restart the IIS Admin service to effect the changes.

For Connection_Abandoned_By_AppPool errors, most of the analyses are due to exceptions of the application, which causes the worker processes in the pool to restart constantly. To this end, I used a global. asax file to take over all unhandled exceptions.

<% @ Application Language = "C #" %>
<% @ Import Namespace = "System. IO" %>

<Script RunAt = "server">
Protected void Application_Error (object sender, EventArgs e)
{
String errorLog = Server. MapPath ("Error. log ");
FileStream fs = new FileStream (errorLog, FileMode. Append, FileAccess. Write );
StreamWriter sw = new StreamWriter (fs );

Sw. writeLine ("Time: {0}, error message: {1}, address: {2}", DateTime. now. toString (), Server. getLastError (). innerException. message, Request. url. absolutePath );
Server. ClearError ();

Sw. Close ();
}
</Script>

Make sure that the debugging mode is set to false in web. config.

Address: http://www.cnblogs.com/chenxizhang/archive/2009/05/31/1492602.html