You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "NAIK,ROSHAN (HP-Cupertino,ex1)" <ro...@hp.com> on 2003/12/16 00:47:54 UTC

mod_jk2 .. is 0 a valid child_id ?

mod_jk2 creates this error long entry each time apache starts up...


[Mon Dec 15 15:20:17 2003] [error] mod_jk child init 1 0


The relevant code printing the error is in function jk2_child_init() in
mod_jk2.c

static void jk2_child_init(apr_pool_t *pconf, server_rec *s)
{
 //...

    if( workerEnv->childId <= 0 ) 
            env->l->jkLog(env, env->l, JK_LOG_ERROR, "mod_jk child init %d
%d\n",
                          workerEnv->was_initialized, workerEnv->childId );
    }
 //...
}


Here 0 is assumed to be invalud childID. But other parts of the code (in the

same function) seem to find the childID>=0 to be fine ....

    if (workerEnv->childId >= 0) {
        workerEnv->childGeneration =
ap_scoreboard_image->parent[workerEnv->childId].generation;
        ++ap_scoreboard_image->parent[workerEnv->childId].generation;
    }

...

    /* Restore the process generation */
    if (workerEnv->childId >= 0) {
        ap_scoreboard_image->parent[workerEnv->childId].generation =
workerEnv->childGeneration;
    }


I am not too clear about the logic ...however it seems like something is 
not right if thar error is being printed each time apache comes up.

-- Roshan 

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org