Julio Cesar Leiva wrote:
Hi all
When we introduce load balancing and a 2nd tomcat worker, the time
to service client requests is not balanced. Some clients are serviced
as above,
but others may take 10, 20, 30 seconds or more. Eventually, clients
timeout
and sessions are lost.
We ran our
Hi all
When we introduce load balancing and a 2nd tomcat worker, the time
to service client requests is not balanced. Some clients are serviced as
above,
but others may take 10, 20, 30 seconds or more. Eventually, clients timeout
and sessions are lost.
We ran our test over night with just 20
Julio,
Double check your httpd.conf to make sure there isn't multiple
MaxClients entries that way you are certain
the one being used us indeed the entry included in the snippet you had
shared with us.
Apache does not throw an error for Duplicate MaxClients entries.
Julio Cesar Leiva wrote:
I double checked just one entry in server-tunning.conf
Gabe Wong wrote:
Julio,
Double check your httpd.conf to make sure there isn't multiple
MaxClients entries that way you are certain
the one being used us indeed the entry included in the snippet you had
shared with us.
Apache does not
Hi all
We have this setup
1 web server apache 2.2.0
2 tomcat servers tomcat 5.5.20
mod_jk 1.2.25
This is our workers.properties
workers.java_home=/usr/lib64/jvm/java
worker.list=cbnbalancer,jkstatus
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
Julio Cesar Leiva wrote:
Hi all
We have this setup
1 web server apache 2.2.0
2 tomcat servers tomcat 5.5.20
mod_jk 1.2.25
This is our workers.properties
workers.java_home=/usr/lib64/jvm/java
worker.list=cbnbalancer,jkstatus
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
Julio Cesar Leiva schrieb:
Hi all
We have this setup
1 web server apache 2.2.0
I hope it's not 2.2.0 but something more recent (e.g. 2.2.4 or 2.2.6)
2 tomcat servers tomcat 5.5.20
mod_jk 1.2.25
This is our workers.properties
Remove the next line, it's useless.
