worker process time limit

Hi,

Just about every 29:07 hrs I get:

----------<quote>---------------------------------
Event Type: Information
Event Source: W3SVC
Event Category: None
Event ID: 1074
Date: 13-11-2007
Time: 8:18:57
User: N/A
Computer: WEBBIE11
Description:
A worker process with process id of '960' serving application pool
'DefaultAppPool' has requested a recycle because the worker process reached
its allowed processing time limit.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
----------<quote>---------------------------------

So I need to find out which process this is. How do I do that? Where can I
find out which process has which Process ID? Is there a HOWTO for this?

Bonno Bloksma

David
Tue Nov 13 23:25:59 PST 2007

On Nov 13, 11:02 pm, "Bonno Bloksma" <tio...@xs4all.nl> wrote:
> Hi,
>
> Just about every 29:07 hrs I get:
>
> ----------<quote>---------------------------------
> Event Type: Information
> Event Source: W3SVC
> Event Category: None
> Event ID: 1074
> Date: 13-11-2007
> Time: 8:18:57
> User: N/A
> Computer: WEBBIE11
> Description:
> A worker process with process id of '960' serving application pool
> 'DefaultAppPool' has requested a recycle because the worker process reached
> its allowed processing time limit.
>
> For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.
> ----------<quote>---------------------------------
>
> So I need to find out which process this is. How do I do that? Where can I
> find out which process has which Process ID? Is there a HOWTO for this?
>
> Bonno Bloksma


I think you don't need to worry about this one.

By default, Application Pools are configured to recycle every 29
hours. This recycling is configured and "expected" and is thus
normally not logged to the event log. IIS doesn't want to worry you
with what you expect. Meanwhile, IIS will log event entries for
unexpected crashes/hangs/stalls of its worker process.

Now, it appears that you have non-default configuration, probably
telling IIS to log ALL recycles, whether expected or unexpected.
Hence, this one shows up. Now, this configuration cannot be done via
the UI, so either you ran a tool that did this intentionally or as a
side-effect, or the server was prepared for you by someone else who
dialed this paranoia knob way up.

But in this case it is really nothing to worry about since nothing is
crashing/hanging. In fact, this event says that nothing crashed/hanged/
misbehaved for the past 29 hours in the DefaultAppPool. Which should
be a good thing.

The process that is being recycled is named "w3wp.exe", and it is a
part of the logical "DefaultAppPool" Application Pool. By the time you
get the event, the process with that PID has already recycled, and it
is not useful to search for that process because nothing bad happened
to trigger that event.

Personally, I would turn that particular event logging off since it is
a false positive, but some people want to know *all* recycles no
matter the reason, hence the feature exists but is not exposed in the
IIS UI anywhere.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Bonno
Wed Nov 14 02:50:26 PST 2007

Hi,

[...]

> Now, it appears that you have non-default configuration, probably
> telling IIS to log ALL recycles, whether expected or unexpected.
> Hence, this one shows up. Now, this configuration cannot be done via
> the UI, so either you ran a tool that did this intentionally or as a
> side-effect, or the server was prepared for you by someone else who
> dialed this paranoia knob way up.

As I installed the server myself.... It is a Windows 2003 R2 server. Maybe
MS changed something to the default settings on that IIS version?
Otherwise, one of our webmasters must have changed something, but they use
IIS manager exclusively.

> But in this case it is really nothing to worry about since nothing is
> crashing/hanging. In fact, this event says that nothing crashed/hanged/
> misbehaved for the past 29 hours in the DefaultAppPool. Which should
> be a good thing.

Ok.

> Personally, I would turn that particular event logging off since it is
> a false positive, but some people want to know *all* recycles no
> matter the reason, hence the feature exists but is not exposed in the
> IIS UI anywhere.

Ok, how do I turn it off?

Bonno Bloksma
CNE MCSE

Kristofer
Wed Nov 14 10:36:15 PST 2007

Hi!

See this documentation:

"Logging Worker Process Recycling Events in IIS 6.0"
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/87892589-4eda-4003-b4ac-3879eac4bf48.mspx?mfr=true

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


Bonno Bloksma wrote:

>Hi,
>
>[...]
>
>>Now, it appears that you have non-default configuration, probably
>>telling IIS to log ALL recycles, whether expected or unexpected.
>>Hence, this one shows up. Now, this configuration cannot be done via
>>the UI, so either you ran a tool that did this intentionally or as a
>>side-effect, or the server was prepared for you by someone else who
>>dialed this paranoia knob way up.
>
>As I installed the server myself.... It is a Windows 2003 R2 server. Maybe
>MS changed something to the default settings on that IIS version?
>Otherwise, one of our webmasters must have changed something, but they use
>IIS manager exclusively.
>
>>But in this case it is really nothing to worry about since nothing is
>>crashing/hanging. In fact, this event says that nothing crashed/hanged/
>>misbehaved for the past 29 hours in the DefaultAppPool. Which should
>>be a good thing.
>
>Ok.
>
>>Personally, I would turn that particular event logging off since it is
>>a false positive, but some people want to know all recycles no
>>matter the reason, hence the feature exists but is not exposed in the
>>IIS UI anywhere.
>
>Ok, how do I turn it off?
>
>Bonno Bloksma
>CNE MCSE

David
Wed Nov 14 15:13:56 PST 2007

On Nov 14, 2:50 am, "Bonno Bloksma" <tio...@xs4all.nl> wrote:
> Hi,
>
> [...]
>
> > Now, it appears that you have non-default configuration, probably
> > telling IIS to log ALL recycles, whether expected or unexpected.
> > Hence, this one shows up. Now, this configuration cannot be done via
> > the UI, so either you ran a tool that did this intentionally or as a
> > side-effect, or the server was prepared for you by someone else who
> > dialed this paranoia knob way up.
>
> As I installed the server myself.... It is a Windows 2003 R2 server. Maybe
> MS changed something to the default settings on that IIS version?
> Otherwise, one of our webmasters must have changed something, but they use
> IIS manager exclusively.
>
> > But in this case it is really nothing to worry about since nothing is
> > crashing/hanging. In fact, this event says that nothing crashed/hanged/
> > misbehaved for the past 29 hours in the DefaultAppPool. Which should
> > be a good thing.
>
> Ok.
>
> > Personally, I would turn that particular event logging off since it is
> > a false positive, but some people want to know *all* recycles no
> > matter the reason, hence the feature exists but is not exposed in the
> > IIS UI anywhere.
>
> Ok, how do I turn it off?
>
> Bonno Bloksma
> CNE MCSE


The default settings for this property has not changed. This is
definitely something local to your installation. Someone has to run
some tool or setup some application which did this change, either
knowingly or unknowingly. You can turn on Metabase Auditing to be able
to track this down in the future.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang