You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Sander de Boer <sa...@list.eo.nl> on 2005/05/19 17:15:40 UTC

locking problem mod_jk 1.2.13 ??

Hi,

I have tested mod_jk 1.2.13. But sometimes my tomcat becomes completely 
be locked for a while. A downgrade to 1.2.10 solves that problem.
So I mean there is a something like a locking problem in 1.2.13, but I 
don't know where and how.

This is my config:
Solaris 8(sparc) / Tomcat 4.1.30 / JDK 1.4.2_06
Solaris 10(sparc) / Apache 2.0.54 / mod_jk_1.2.13

workers.properties:
----
ps=/

worker.list=loadbalancer,status,wss01

worker.mmbase03.port=8082
worker.mmbase03.host=10.0.0.208
worker.mmbase03.type=ajp13
worker.mmbase03.lbfactor=100
worker.mmbase03.disabled=false

worker.mmbase04.port=8082
worker.mmbase04.host=10.0.0.228
worker.mmbase04.type=ajp13
worker.mmbase04.lbfactor=100
worker.mmbase04.disabled=true

worker.loadbalancer.type=lb
worker.loadbalancer.balance_workers=mmbase03,mmbase04
----

Any ideas?

Cheers,
Sander

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


Re: locking problem mod_jk 1.2.13 ??

Posted by Mladen Turk <ml...@jboss.com>.
Sander de Boer wrote:
> Hi,
> 
> I have tested mod_jk 1.2.13. But sometimes my tomcat becomes completely 
> be locked for a while. A downgrade to 1.2.10 solves that problem.
> So I mean there is a something like a locking problem in 1.2.13, but I 
> don't know where and how.
>

Is tomcat locked or your response is sometimes slow?
If the response is slow set the:
worker.mmbaseXX.socket_timeout=10

Other option is to set the
worker.loadbalancer.retries=1

The problem is related with Tomcat 4.1.x closing its
side of connection after 30 seconds of inactivity,
so you can set the connectionTimeout="0" in server.xml
or use socket_timeout with lower value (60 seconds by
system default).
Using connectionTimeout="0" is the best way (default on
Tomcat5) but you'll have to be sure that maxTreads in
server xml equals MaxClients in httpd.conf.

Further option is to set the
worker.mmbaseXX.prepost_timeout=10000
if the socket_timeout doesn't work on Solaris.

Unlike 1.2.10 mod_jk 1.2.13 correctly handles that case
without loosing session affinity that might happen on
earlier versions.

Regards,
Mladen.

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