Need help with system event log error on IIS 6.0

Need help with system event log error on IIS 6.0

Post by Jeremy Smi » Sat, 25 Dec 2004 02:02:48


Event ID: 1025
Application pool 'default' exceeded its job limit settings.


What is the best way to trouble shoot this error?

Application configuration:
I have memory setup to recycle at 1000mb virtual memory and 300mb used
memory. I also have CPU monitoring to shut down worker process at 95%.

Additional info:
I get the above error about 3 times a day. I have ran Perfmon to
monitor the server resources. The server resources never get close to
the above limits. The site get very little traffic.
 
 
 

Need help with system event log error on IIS 6.0

Post by David Wang » Sun, 26 Dec 2004 03:12:41

What sort of application are you running? ASP/ASP.Net/PHP/etc?
What is the physical RAM in the machine?

I suspect your Application configuration is wrong for your web application.

--
//David
IIS
http://www.yqcomputer.com/
This posting is provided "AS IS" with no warranties, and confers no rights.
//


Event ID: 1025
Application pool 'default' exceeded its job limit settings.


What is the best way to trouble shoot this error?

Application configuration:
I have memory setup to recycle at 1000mb virtual memory and 300mb used
memory. I also have CPU monitoring to shut down worker process at 95%.

Additional info:
I get the above error about 3 times a day. I have ran Perfmon to
monitor the server resources. The server resources never get close to
the above limits. The site get very little traffic.

 
 
 

Need help with system event log error on IIS 6.0

Post by Jeremy Smi » Wed, 05 Jan 2005 04:17:25


application.


ASP

3.5 GB physical ram.
4 x 2GHz Xeon CPU

I think it might be do to high CPU for a few seconds.
Thanks for your help
 
 
 

Need help with system event log error on IIS 6.0

Post by David Wang » Thu, 06 Jan 2005 02:27:41

I think it is a CPU spike that triggered the CPU Limit-based recycle.

I think you need to decide whether your metric is correct (i.e. you *should*
be getting the event log warnings and should be figuring out why your ASP
app would spike the CPU), or the metric is incorrect and should be adjusted.

If the server can be debugged, I suggest looking up the AppPool property
OrphanActionExe, which allows you to configure a command to run when IIS is
going to recycle/abandon an application pool. In your case, you want to
configure it to run a command like adplus or iisstate to take a snapshot of
the process so that you can see *what* is spiking the CPU. I suspect it
will be something in your ASP page, and this can help narrow down which page
and what sort of action it was doing.

OrphanActionExe
http://www.yqcomputer.com/
I remember you can use %1, %2, etc for w3wp PID, w3wp AppPoolId, .etc, but
not certain of which (I believe %1 = PID, %2 = failure reasonn, %3 =
AppPoolId), and it does not appear to be in documentation. I'll open a
documentation bug on it, but in the meantime, you can quickly experiment and
figure out which.

IISState
http://www.yqcomputer.com/

ADPlus
http://www.yqcomputer.com/ ;en-us;286350

--
//David
IIS
http://www.yqcomputer.com/
This posting is provided "AS IS" with no warranties, and confers no rights.
//




application.


ASP

3.5 GB physical ram.
4 x 2GHz Xeon CPU

I think it might be do to high CPU for a few seconds.
Thanks for your help