httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manoj Kasichainula <man...@io.com>
Subject Re: threaded apache question
Date Mon, 21 Jun 1999 18:29:18 GMT
On Mon, Jun 21, 1999 at 01:55:56AM -0700, Tani Hosokawa wrote:
> .K...K......W....L..W.....W.K....K..........W...K....K.........W
> .......K.W......................................................
> ..W.W.W.....W.....W....W......................................K.
> .W..............................................................
> .............................W........W.........................
> ..........W.....................................................
> ..............W.................................................
> ..W.KW.........W.W....K........W.....WWW.K....W.................
> W...........W................K....K.............................
> 
> If I understand what you're saying correctly, each process should always
> have 64 threads, with some just being inactive (marked by _, not .),
> correct?

Correct.

It looks like all of these processes is trying to die from hitting
MaxRequestsPerChild (or did something initiate a graceful restart?),
but not all of the threads are reaching the point where they learn
it's time to die.

Could you attach a debugger to some of these errant threads to see
what they're actually doing? Are they hung on a socket, like you were
describing for 1.3?

Also, what is MaxRequestsPerChild set to? I haven't seen any
MaxRequestsPerChild bugs in the code lately, but some could still be
lurking.

-- 
Manoj Kasichainula - manojk at io dot com - http://www.io.com/~manojk/
"The early bird who catches the worm works for someone who comes in late
and owns the worm farm." -- Travis McGee

Mime
View raw message