i think the answer to aaron's question is "a typo". otherwise there is

actually 1 less thread available to serve requests than configured.
PR:
Obtained from:
Submitted by:
Reviewed by:

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@90670 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/server/mpm/worker/worker.c b/server/mpm/worker/worker.c
index a56b1f9fff40d7f2f7be562a030983b4d5a5d4e9..18244a2703ac3902a92f7a16a005a3c36d474060 100644 (file)
--- a/server/mpm/worker/worker.c
+++ b/server/mpm/worker/worker.c
@@ -755,9 +755,8 @@ static void *start_threads(apr_thread_t *thd, void * dummy)
     my_info->sd = 0;
     apr_thread_create(&listener, thread_attr, listener_thread, my_info, pchild);
     while (1) {
-        /* Does ap_threads_per_child include the listener thread?
-         * Why does this forloop start at 1? -aaron */
-        for (i = 1; i < ap_threads_per_child; i++) {
+        /* Does ap_threads_per_child include the listener thread? */
+        for (i = 0; i < ap_threads_per_child; i++) {
             int status = ap_scoreboard_image->servers[child_num_arg][i].status;
 
             if (status != SERVER_GRACEFUL && status != SERVER_DEAD) {