tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Lonsdale <LON...@uk.ibm.com>
Subject Round Robin
Date Thu, 16 Aug 2007 21:04:08 GMT
Hi all

We are currently trying to setup load balancing in our environment and as 
after testing the Load Balancing it would appear to be working. I have run 
up two applications sessions, one of which went to the 'A' tomcat worker 
and the other to the 'C' tomcat worker. The status page suggests that the 
workers are load balanced, although as yet the 'B' worker has only ever 
appeared with a status of 'N/A' (Unknown). Other workers have appeared 
with a status of 'OK'.
 
I suspect that this load balancer is not using  a 'Round Robin' algorithm. 
I also cannot see any way of setting this as a Load Balancer method. Below 
is our workers.properties file, could anyone please advise why a round 
robin approach may not be working pls ?

thanks in advance

# ==============================================================
# JK configuration directives
# ==============================================================
ps=/

# ==============================================================
# list the workers required as entry points from apache  by name
# ==============================================================

worker.list= ajp13, loadbalancer , status

# ==============================================================
# Single worker to handle all non load balanced requests
# (Esri IMS)
# ==============================================================

worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13

# ==============================================================
# Balanced set of workers to handle all load balanced requests
# (IMF Easimap)
# ==============================================================

# ---------------------------
# 1st Balanced worker Tomcat1
# ---------------------------

worker.tomcat1.port=8109
worker.tomcat1.host=localhost
worker.tomcat1.type=ajp13
worker.tomcat1.socket_keepalive=1
worker.tomcat1.socket_timeout=600
worker.tomcat1.lbfactor=100
worker.tomcat1.route=tomcat5_A
worker.tomcat1.connection_pool_timeout=300

# ---------------------------
# 2nd Balanced worker Tomcat2
# ---------------------------

worker.tomcat2.port=8209
worker.tomcat2.host=localhost
worker.tomcat2.type=ajp13
worker.tomcat2.socket_keepalive=1
worker.tomcat2.socket_timeout=600
worker.tomcat2.lbfactor=100
worker.tomcat2.route=tomcat5_B
worker.tomcat2.connection_pool_timeout=300

# ---------------------------
# 3rd Balanced worker Tomcat3
# ---------------------------

worker.tomcat3.port=8309
worker.tomcat3.host=localhost
worker.tomcat3.type=ajp13
worker.tomcat3.socket_keepalive=1
worker.tomcat3.socket_timeout=600
worker.tomcat3.lbfactor=100
worker.tomcat3.route=tomcat5_C
worker.tomcat3.connection_pool_timeout=300

#--------------------------
# Tomcat balancer
#--------------------------
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=tomcat1, tomcat2, tomcat3


# ==============================================================
# Tomcat status worker - gives status information on connected
# instances
# ==============================================================

worker.status.type=status






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU






Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message