Our application which runs on Apache HTTP Server 2.0.54, TOMCAT 5.0.28 with
mod_jk 1.2.15 connector. In production while our application was running.
Our application had a thread dead Lock hosing up all the users trying to
connect our application. So started investigating the failover setup in
Mott Leroy wrote:
I was wondering if I could get some advice on better failover for my
current setup. I'm using mod_jk 1.2.14 with Tomcat 5.0.28.
One issue that we occassionally run across is that an instance of tomcat
will become unresponsive (due to out of memory errors for example) but
Mladen Turk wrote:
Yes, use the 'Advanced worker directives'
http://tomcat.apache.org/connectors-doc/config/workers.html
The connect_timeout, prepost_timeout and reply_timeout are meant to
be used with hanged or very busy backend (Tomcat) servers.
Thanks.
I'm having trouble understanding
Subject: robust Failover, mod_jk
I was wondering if I could get some advice on better failover for my
current setup. I'm using mod_jk 1.2.14 with Tomcat 5.0.28.
One issue that we occassionally run across is that an instance of tomcat
will become unresponsive (due to out of memory errors
Duan, Nick wrote:
Apparently mod_jk does support several load balancing algorithms other
than round-robin. You may want to set the method property of load
balancer to Request or Traffic. See instructions on worker properties
for details.
Mott Leroy wrote:
Mladen Turk wrote:
Yes, use the 'Advanced worker directives'
http://tomcat.apache.org/connectors-doc/config/workers.html
The connect_timeout, prepost_timeout and reply_timeout are meant to
be used with hanged or very busy backend (Tomcat) servers.
I'm having trouble
