Hi,
Not sure if I'm sending this question to the right forum, but
anyway I will try as anybody might have experienced this already.
 I'm trying to loadbalance (no clustering, session replication...)
our web application by using tomcat (2 instances) + httpd + mod_jk module
and have run into the folowing problems.
 When I login usually a front page opens and than I'm redirected
back to the login page. Sometimes when I start I get into the front
page, but only some parts are displayed (but after few seconds
if I logout I can not login again)
We're using frames + struts so one user request results to
many requests to the server.
 If I leave only one instance of tomcat running the web application
works normaly.
 It looks like a session or timeout problems. Like the loadbalancer would
be splitting those requests (one user request - login) to multiple
tomcat instances, which will cause the application to redirect the control
to the login page.
 We are also using SSL (not sure if it affects something)
 Here is my workers.properties
Thanks a lot for any help.

#properties
workers.ajp13.1.host=127.0.0.1
workers.ajp13.1.port=8009
workers.ajp13.2.host=xx.xx.xx.xx (other server IP)
workers.ajp13.2.port=8009

worker.list=loadbalancer, ajp13.1, ajp13.2

worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=ajp13.1, ajp13.2
worker.loadbalancer.sticky_session=True

# Workers
worker.ajp13.1.port=$(workers.ajp13.1.port)
worker.ajp13.1.host=$(workers.ajp13.1.host)
worker.ajp13.1.type=ajp13
worker.ajp13.1.lbfactor=1
worker.ajp13.1.cachesize=10
worker.ajp13.1.cache_timeout=600
worker.ajp13.1.socket_timeout=180
worker.ajp13.1.socket_keepalive=1
worker.ajp13.1.recycle_timeout=300
the other one is the same...

Reply via email to