tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikola Milutinovic" <Nikola.Milutino...@ev.co.yu>
Subject Re: jk2_init() Can't find child xxxx in none of the 1024 scoreboard slots
Date Sun, 04 Jan 2004 12:01:04 GMT
Subject: Fw: jk2_init() Can't find child xxxx in none of the 1024 scoreboard
slots


> Hi Peter,
>
> I'm using Apache 2.0.48, Tomcat 4.1.29, Jakarta-Tomcat-Connectors 4.1.29.
> I'm hoping the problem it is not the mod_jk2.so module as I went to great
> trouble in order to generate it on my RH9 Linux Kernal Version 2.4.20-8
> platform. I had to recompile apr, apr-util code and only "ant native"
> managed to build mod_jk2.so

> ### error.log file in Apache2.0.48 log
> ###########################################
> [Sat Jan 03 23:01:48 2004] [error] jk2_init() Can't find child 7398 in
none
> of the 256 scoreboard slots
> [Sat Jan 03 23:01:48 2004] [error] jk2_init() Can't find child 7399 in
none
> of the 256 scoreboard slots
> [Sat Jan 03 23:01:48 2004] [error] jk2_init() Can't find child 7400 in
none
> of the 256 scoreboard slots
> [Sat Jan 03 23:01:48 2004] [error] jk2_init() Can't find child 7402 in
none
> of the 256 scoreboard slots
> [Sat Jan 03 23:01:48 2004] [notice] Apache/2.0.48 (Unix) mod_jk2/2.0.3-dev
> configured -- resuming normal operations

These are mostly harmless messages. The only way I found to avoid them was a
rather long one.

In order for Apache + mod_jk2 to find neighbour children is to configure
shared memory for mod_jk2. And it must be configured on both Apache and
Tomcat side. If you drop Tomcat side, then it will complain. :-)

For shared memory in Coyote-jk2 handler, you need to build jkjni.so (you may
screem in agony :-)). JK-JNI gives you "Java Native Interface"
functionality, which includes UNIX SHM and UNIX file sockets.

In order for jkjni.so to function correctly, it must have an environment
variable "serverRoot" defined on the process level, or it will not be able
to locate workers2.properties (it is in Apache's config dir). To be honest,
jkjni.so was designed for another purpose - running Tomcat from within
Apache process (in-process). This environment variable is provided by
Apache. All of us who wish to run a standalone Tomcat and still use jkjni.so
must emulate this. The only way I found to do that was to place

export serverRoot=/etc/httpd/2.0

in Tomcat's config/startup scripts. Like I said - it is long one.

> [Sun Jan 04 12:08:37 2004] [notice] caught SIGTERM, shutting down

Normal shutdown, I'd say.

> ####################### jk2.prorperties ###########################
> ## THIS FILE MAY BE OVERRIDEN AT RUNTIME. MAKE SURE TOMCAT IS STOPED
> ## WHEN YOU EDIT THE FILE.
> ## COMMENTS WILL BE _LOST_
> ## DOCUMENTATION OF THE FORMAT IN JkMain javadoc.
> # Set the desired handler list
> # handler.list=apr,request,channelJni

Why are you using "channelJni"?

You could use "apr,request,channelSocket" and drop JNI completely. Take look
at Tomcats docs and JK2 section.

> ########################## workers.properties ####################
> worker.list=ajp13
> worker.ajp13.port=8009
> worker.ajp13.host=localhost
> worker.ajp13.type=ajp13
> ############################################################

Why are you using "workers.properties"? It is for mod_jk. For mod_jk2 you
must use "worker2.properties".

Consult docs at http://jakarta.apache.org -> Tomcat -> Documentation.

Nix.


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


Mime
View raw message