Hi All,

Tomcat 6.0.29 with Apache 2.2.17 running on windows 2003R2
Currently the workers.properties files is setup like this and seems to be 
working fine.

Current Setup
worker.list=part
#worker.list=worker1, worker2

#
# Defining a worker named ajp13w and of type ajp13
# Note that the name and the type do not have to match.
#
worker.jvm1.type=ajp13
worker.jvm1.host=10.17.75.145
worker.jvm1.port=8019
worker.jvm1.lbfactor=10

worker.jvm2.type=ajp13
worker.jvm2.host=10.17.75.145
worker.jvm2.port=8029
worker.jvm2.lbfactor=10

worker.jvm1.type=ajp13
worker.jvm1.host=10.17.75.61
worker.jvm1.port=8019
worker.jvm1.lbfactor=10

worker.jvm2.type=ajp13
worker.jvm2.host=10.17.75.61
worker.jvm2.port=8029
worker.jvm2.lbfactor=10

worker.part.type=lb
worker.part.balance_workers=jvm1,jvm2
worker.part.sticky_session=1

Please note that I have two different IP addresses running under the same 
worker.  My boss thinks that this is causing sessions to jump between the two 
ip addresses on the same jvm.
Question
Is the current configuration incorrect?  I don't think so but can't find 
anything anywhere else to back me up.  Reasoning being that workers.properties 
has the IP address defined in it.  So the request would go to jvm1 ip 
10.17.75.61 if jvm1 ip 10.17.75.61 is down or not available it won't try to go 
to jvm1 10.17.75.145 because the host info (ip address) isn't the same.

Jvm1- TC instance1
Jvm2- TC instance2

Thanks in advance,
Martin

Reply via email to