tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <mladen.t...@jboss.com>
Subject Re: [mod_jk] concurrency control problem
Date Thu, 22 Dec 2005 11:19:23 GMT
Grzegorz TaƄczyk wrote:
> Hello Mladen,
> 
> MT> Perhaps posting workers.properties would help.
> worker.w1.type=ajp13
> worker.w1.host=localhost
> worker.w1.port=8000
> worker.w1.cachesize=200
> worker.w1.cache_timeout=300
> worker.w1.socket_timeout=300
> worker.w1.socket_keepalive=0
> worker.w1.recycle_timeout=100
> worker.w1.recovery_options=3
> worker.w1.prepost_timeout=100000
> worker.w1.connect_timeout=100000
> worker.w1.reply_timeout=100000
> 
> Other w2 and w3 have cachesize 100. cache_timeout unit is second or
> milisecond?
>

miliseconds.

You will need to lower the:
worker.w1.cachesize=maxThreads(server.xml)/ServerLimit (httpd.conf)

So if you wish to have no more then 200 connections to Tomcat/worker
and you have 1000 MaxClients with 25 ThreadsPerChild.
This will give you max of 40 Servers.
Now divide 200/40 and that is your cachesize (5 in that case).

If you start receiving 503 (Server Busy), Increase the maxThreads
and cachesize or add retries=60 for lb worker.

Regards,
Mladen.

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


Mime
View raw message