Re: Is it advisable NOT to limit MaxRequestsPerChild in Win32 modperl?

["Lionel MARTIN" <suppressed>]

Unless I'm mistaken, and even if there is only one (child) Apache process 
and several thread under Windows (winnt MPM), the only directive that can be 
used is MaxRequestsPerChild  and not MaxRequestsPerThread.

It is not possible to restart individual threads (and associated Perl 
Interpreteers), but only restart the child (which means restarting all the 
threads at once). So, basically, the value indicated by MaxRequestsPerChild 
is shared among all threads. (and its defaults value is 0, which means that 
your child is never restarted because of having handled too many requests).

That's a bit of pity, because that's like an "all or nothing" behaviour, you 
can't kill individual threads because they are growing too much.

Lionel.

----- Original Message ----- 
From: "Perrin Harkins" <suppressed>
To: "Foo JH" <suppressed>
Cc: <suppressed>
Sent: Friday, May 25, 2007 7:05 AM
Subject: Re: Is it advisable NOT to limit MaxRequestsPerChild in Win32 
modperl?


> On 5/24/07, Foo JH <suppressed> wrote:
> > This I
> > accomplish by setting a small number (for testing) to
> > MaxRequestsPerChild to see how modperl recovers from a reload.
>
> I think you're looking for MaxRequestsPerThread.  There is only one
> process on the Windows MPM.
>
> - Perrin