On 22 Feb 2001, Jeff Trawick wrote:
> [EMAIL PROTECTED] writes:
>
> > ThreadsPerChild should NOT include the signal thread. That directive
> > talks about how many worker threads you have, not total threads.
>
> Okay, I'm glad we're on the same page!
>
> What is the explanation for the " - 1" in the next expression which
> controls how many threads we create in the new child?
>
> for (i=0; i < ap_threads_per_child - 1; i++) {
Previously, we created ap_threads_per_child threads, and the original
thread became the signal thread. With the new logic, we create a separate
thread for the signal thread, so the original thread becomes one of the
worker threads. The -1 is so that we don't create ThreadsPerChild +1
threads on startup.
> 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.
Ryan
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
