You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by James Masson <ja...@inspiredbroadcast.net> on 2007/01/31 11:40:58 UTC
mod_jk - more than 15 workers = hang
Hi,
I'm working on creating a pair of Apache mod_jk load balancers for an Tomcat web-app farm.
Redhat ES4
Server Version: Apache/2.0.52 (Red Hat)
JK Version: mod_jk/1.2.20
apache-tomcat-5.5.20-1
Everything works fine, until I exceed 15 load balancing workers on mod_jk, then I get a 500-Internal
Server Error, for every web-app.
Note that the 16th worker config works fine, if specified as part of the 15.
Error messages aren't much help, but are included below.
I've tried doubling all the MPM worker values in httpd.conf - no effect.
Any clues to what's going wrong?
thanks
James Masson
###############
[Wed Jan 31 09:55:09 2007] [32523:1728] [error] validate::jk_lb_worker.c (1206): allocating worker
record from shared memory
[Wed Jan 31 09:55:09 2007] [32523:1728] [error] wc_create_worker::jk_worker.c (161): validate failed
for managementLogic
[Wed Jan 31 09:55:09 2007] [32523:1728] [error] build_worker_map::jk_worker.c (259): failed to
create worker managementLogic
[Wed Jan 31 09:55:09 2007] [32524:1728] [error] validate::jk_lb_worker.c (1206): allocating worker
record from shared memory
[Wed Jan 31 09:55:09 2007] [32524:1728] [error] wc_create_worker::jk_worker.c (161): validate failed
for managementLogic
[Wed Jan 31 09:55:09 2007] [32524:1728] [error] build_worker_map::jk_worker.c (259): failed to
create worker managementLogic
[Wed Jan 31 10:37:08 2007] [32608:63168] [debug] map_uri_to_worker::jk_uri_worker_map.c (587):
Attempting to map context URI '/status/*=jkstatus' source 'JkMount'
[Wed Jan 31 10:37:08 2007] [32608:63168] [debug] map_uri_to_worker::jk_uri_worker_map.c (602): Found
a wildchar match '/status/*=jkstatus'
[Wed Jan 31 10:37:08 2007] [32608:63168] [debug] jk_handler::mod_jk.c (1999): Into handler
jakarta-servlet worker=jkstatus r->proxyreq=0
[Wed Jan 31 10:37:08 2007] [32608:63168] [debug] wc_get_worker_for_name::jk_worker.c (114): did not
find a worker jkstatus
[Wed Jan 31 10:37:08 2007] [32608:63168] [info] jk_handler::mod_jk.c (2150): Could not find a
worker for worker name=jkstatus
**********************************************************************
Confidentiality : This e-mail and any attachments are intended for the addressee only and may be confidential. If they come to you in error you must take no action based on them, nor must you copy or show them to anyone. Please advise the sender by replying to this e-mail immediately and then delete the original from your computer.
Opinion : Any opinions expressed in this e-mail are entirely those of the author and unless specifically stated to the contrary, are not necessarily those of the authors employer.
Security Warning : Internet e-mail is not necessarily a secure communications medium and can be subject to data corruption. We advise that you consider this fact when e-mailing us.
Viruses : We have taken steps to ensure that this e-mail and any attachments are free from known viruses but in keeping with good computing practice, you should ensure that they are virus free.
Inspired Gaming (UK) Limited
Registered in England No 3565640
Registered Office 3 The Maltings Wetmore Road, Burton On Trent, Staffordshire DE14 1SE
_______________________________________________________________
This message has been checked for all known viruses by the MessageLabs Virus Control Centre.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: mod_jk - more than 15 workers = hang
Posted by James Masson <ja...@inspiredbroadcast.net>.
JkShmSize 256
That solved the problem - Thanks to all who replied!
>>
>> Note that the 16th worker config works fine, if specified as part of
>> the 15.
>
> I don't understand, what you mean by specifying a worker as part of
> another worker.
>
I was just saying that the problem wasn't a specific web-app or config - any 16th web-app would do it.
regards
James
Rainer Jung wrote:
> Hi James,
>
> I guess, the size of the shared memory is not big enough.
> You can increase it using the JkShmSize directive for Apache. The value
> is an integer value which is the provided shared memory size in Kilobytes.
>
> During startup with JkLogLevel debug you get messages like:
>
> ... do_shm_open::jk_shm.c (327): Truncated shared memory to 28800
> ... do_shm_open::jk_shm.c (360): Initialized shared memory size=28800
> free=28672 addr=0x2a98f02000
> ... do_shm_open_lock::jk_shm.c (266): Opened shared memory lock
> /var/tmp/install/apache2p/logs/jk-runtime-status.lock
> ... init_jk::mod_jk.c (2562): Initialized
> shm:/var/tmp/install/apache2p/logs/jk-runtime-status
>
> from which you can see, which file system object is used for the shared
> mem and which size is used. Usually the size should be big enough to
> handle 64 workers (including ajp13, load balancers and lb sub workers).
>
> You can check, the size that is being used on your system and then
> double it via JkShmSize and try again. Let us know your results.
>
> One question:
>
> James Masson wrote:
>>
>> Hi,
>>
>> I'm working on creating a pair of Apache mod_jk load balancers for an
>> Tomcat web-app farm.
>>
>> Redhat ES4
>> Server Version: Apache/2.0.52 (Red Hat)
>> JK Version: mod_jk/1.2.20
>>
>> apache-tomcat-5.5.20-1
>>
>> Everything works fine, until I exceed 15 load balancing workers on
>> mod_jk, then I get a 500-Internal Server Error, for every web-app.
>>
>> Note that the 16th worker config works fine, if specified as part of
>> the 15.
>
> I don't understand, what you mean by specifying a worker as part of
> another worker.
>
> Regards,
>
> Rainer
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
> _____________________________________________________________________
> This e-mail has been scanned for viruses by MessageLabs.
**********************************************************************
Confidentiality : This e-mail and any attachments are intended for the addressee only and may be confidential. If they come to you in error you must take no action based on them, nor must you copy or show them to anyone. Please advise the sender by replying to this e-mail immediately and then delete the original from your computer.
Opinion : Any opinions expressed in this e-mail are entirely those of the author and unless specifically stated to the contrary, are not necessarily those of the authors employer.
Security Warning : Internet e-mail is not necessarily a secure communications medium and can be subject to data corruption. We advise that you consider this fact when e-mailing us.
Viruses : We have taken steps to ensure that this e-mail and any attachments are free from known viruses but in keeping with good computing practice, you should ensure that they are virus free.
Inspired Gaming (UK) Limited
Registered in England No 3565640
Registered Office 3 The Maltings Wetmore Road, Burton On Trent, Staffordshire DE14 1SE
_______________________________________________________________
This message has been checked for all known viruses by the MessageLabs Virus Control Centre.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: mod_jk - more than 15 workers = hang
Posted by Rainer Jung <ra...@kippdata.de>.
Hi James,
I guess, the size of the shared memory is not big enough.
You can increase it using the JkShmSize directive for Apache. The value
is an integer value which is the provided shared memory size in Kilobytes.
During startup with JkLogLevel debug you get messages like:
... do_shm_open::jk_shm.c (327): Truncated shared memory to 28800
... do_shm_open::jk_shm.c (360): Initialized shared memory size=28800
free=28672 addr=0x2a98f02000
... do_shm_open_lock::jk_shm.c (266): Opened shared memory lock
/var/tmp/install/apache2p/logs/jk-runtime-status.lock
... init_jk::mod_jk.c (2562): Initialized
shm:/var/tmp/install/apache2p/logs/jk-runtime-status
from which you can see, which file system object is used for the shared
mem and which size is used. Usually the size should be big enough to
handle 64 workers (including ajp13, load balancers and lb sub workers).
You can check, the size that is being used on your system and then
double it via JkShmSize and try again. Let us know your results.
One question:
James Masson wrote:
>
> Hi,
>
> I'm working on creating a pair of Apache mod_jk load balancers for an
> Tomcat web-app farm.
>
> Redhat ES4
> Server Version: Apache/2.0.52 (Red Hat)
> JK Version: mod_jk/1.2.20
>
> apache-tomcat-5.5.20-1
>
> Everything works fine, until I exceed 15 load balancing workers on
> mod_jk, then I get a 500-Internal Server Error, for every web-app.
>
> Note that the 16th worker config works fine, if specified as part of the
> 15.
I don't understand, what you mean by specifying a worker as part of
another worker.
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: mod_jk - more than 15 workers = hang
Posted by Mladen Turk <ml...@gmail.com>.
James Masson wrote:
>
> Hi,
>
> I'm working on creating a pair of Apache mod_jk load balancers for an
> Tomcat web-app farm.
>
> Redhat ES4
> Server Version: Apache/2.0.52 (Red Hat)
> JK Version: mod_jk/1.2.20
>
> apache-tomcat-5.5.20-1
>
> Everything works fine, until I exceed 15 load balancing workers on
> mod_jk, then I get a 500-Internal Server Error, for every web-app.
>
> Note that the 16th worker config works fine, if specified as part of the
> 15.
>
Add
JkShmSize 128
to the configuration.
It will allocate enough room (128 kB) for more then 15 workers.
Regards,
Mladen.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org