Workerprocess

#1 08-08-2008, 02:48 AM

Hi,

Win2003, IIS6:

Under ApplicationPool/Properties the idle timeout in minutes is not
activated. I think, that I have a better performance with this setting.
Could this setting still give me some problems in the near future?

I think becaus of this setting I have an event under system with id 1074
from the source W3SVC:
A worker process with process id of "<process id>" serving application pool
"DefaultAppPool" has requested a recycle because the worker process reached
its allowed processing time limit.

The type of the event is an information and NOT an error.

Can I still leave the above setting inactive?

Thanks for your hint.

Patrick

#2 08-08-2008, 04:17 AM

On Aug 7, 11:48*pm, Patrick D. <Patri...@discussions.microsoft.com>
wrote:
> Hi,
>
> Win2003, IIS6:
>
> Under ApplicationPool/Properties the idle timeout in minutes is not
> activated. I think, that I have a better performance with this setting.
> Could this setting still give me some problems in the near future?
>
> I think becaus of this setting I have an event under system with id 1074
> from the source W3SVC:
> A worker process with process id of "<process id>" serving application pool
> "DefaultAppPool" has requested a recycle because the worker process reached
> its allowed processing time limit.
>
> The type of the event is an information and NOT an error.
>
> Can I still leave the above setting inactive?
>
> Thanks for your hint.
>
> Patrick

The setting does not give any problems on its own. If it gave problems
on its own, then it wouldn't be a setting worth turning on. Every IIS
setting has at least one reason to be turned on, and at least one
reason to be turned off.

Thus, the answer to your question really depends on your application
and how it interacts with a given setting.

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

#3 08-08-2008, 04:36 AM

Thanks David:

You are right, there must be at least one reason not to timeout workerprocess.
As long as I have no errors I will not change this setting.

Patrick

"David Wang" wrote:

> On Aug 7, 11:48 pm, Patrick D. <Patri...@discussions.microsoft.com>
> wrote:
> > Hi,
> >
> > Win2003, IIS6:
> >
> > Under ApplicationPool/Properties the idle timeout in minutes is not
> > activated. I think, that I have a better performance with this setting.
> > Could this setting still give me some problems in the near future?
> >
> > I think becaus of this setting I have an event under system with id 1074
> > from the source W3SVC:
> > A worker process with process id of "<process id>" serving application pool
> > "DefaultAppPool" has requested a recycle because the worker process reached
> > its allowed processing time limit.
> >
> > The type of the event is an information and NOT an error.
> >
> > Can I still leave the above setting inactive?
> >
> > Thanks for your hint.
> >
> > Patrick
>
>
> The setting does not give any problems on its own. If it gave problems
> on its own, then it wouldn't be a setting worth turning on. Every IIS
> setting has at least one reason to be turned on, and at least one
> reason to be turned off.
>
> Thus, the answer to your question really depends on your application
> and how it interacts with a given setting.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode