IIS utility for applications is removed randomly every few seconds

Question

I need to determine WHY the application pool is being recycled. (its for obvious reason)

Is there a way to define this inside the application_end subdirectory in the global.asax file?

I added some master notes, so I know WHEN it closes, but I can’t understand why.

(and its nothing obvious ... It seems that every pair of requests causes the application to end. I turned off all the usual reasons for reuse, such as timeouts, memory checks, etc. etc. etc. .d. The same code works fine on another server, so I'm sure that something is wrong with this setting, but what? ...)

Answer 1

You do not need to impose overhead to add a user log, monitoring the health of ASP.NET 2.0 does the job for you. You can add the following configuration, which will log events in the event logs with information on why the application pool is restarting.

To enable ASP.NET health monitoring, you can edit the "master" web.config , usually located in the %systemroot%\microsoft.net\framework\v2.0.50727\config .

• First find <healthMonitoring> in the main web.config

• healthMonitoring node healthMonitoring node <rules>

• Inside the rules add the following:

   <add name="Application Lifetime Events Default" eventName="Application Lifetime Events" provider="EventLogProvider" profile="Default" minInstances="1" maxLimit="Infinite" minInterval="00:01:00" custom="" /> 

Reproduce the problem and look in the fpr application event log for ASP.NET 2.0 source. This should be logged why the application pool is being processed.

Answer 2

Try looking at EventLog. When the application pool is processed, the entry is written to the log along with the reason.

The following link describes the error codes that you will see in the event log for IIS 7.5 http://technet.microsoft.com/en-us/library/dd349270(WS.10).aspx

Answer 3

If your event handler with problematic machines does not yet have log entries, you can modify IIS to record all repeated cycles of the application pool.

Microsoft's article on how to do this is below.

http://support.microsoft.com/kb/332088