Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 55869 invoked by uid 500); 22 Feb 2001 21:24:10 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 55838 invoked from network); 22 Feb 2001 21:24:07 -0000 Date: Thu, 22 Feb 2001 05:22:23 -0800 (PST) From: X-Sender: To: Subject: Re: ThreadsPerChild - should it include the implicit signal thread? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > > > Besides not starting enough worker threads per child, the scoreboard > > > maintenance is also confused because the SERVER_DEAD entry > > > (uninitialized) in the slot for thread ap_threads_per_child-1 keeps it > > > from counting the threads of that child in the number of idle threads. > > > > I don't really understand this, because worker_thread should have just > > handled all of this stuff. > > the problem is pretty simple: > > only creating ap_threads_per_child-1 worker threads means we only use > elements 0..ap_threads_per_child-2 of the scoreboard array for this > child; idle-server-maintenance logic looks in elements > 0..ap_threads_per_child-1 of the scoreboard array for each child; when > it finds any element which has the uninitialized/SERVER_DEAD value > then bad stuff happens (like not counting any of the idle threads in > that child towards the number of overall idle threads); thus bad stuff > happens since element [ap_threads_per_child-1] is uninitialized But worker_thread should have initialized the scoreboard correctly, so that element ap_threads_per_child - 1 does have an actual value. Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------