Hi,

I am using Apache 2.0.46 with tomcat 4.1.18. I recently configured
the high availability (load balancing), but did not give the sticky
sessions.

Can any one let me know how to do that and also what is the disadvantage if i do not configure sticky sessions?

Any help is thankful.
Regards
Subir S

Hi there,
if you are working with mod_jk the default loadbalancer (type lb) has sticky session enabled by default providing you have setup your jmRoute properly in each catalina engine (server.xml on each server) [or at least that how I understand it]

(extract from the workers.properties)
#------ DEFAULT LOAD BALANCER WORKER DEFINITION ----------------------
#---------------------------------------------------------------------
#

#
# The loadbalancer (type lb) workers perform wighted round-robin
# load balancing with sticky sessions.
# Note:
# ----> If a worker dies, the load balancer will check its state
# once in a while. Until then all work is redirected to peer
# workers.
#worker.loadbalancer.type=lb
#worker.loadbalancer.balanced_workers=yourworker


If you do not apply the sticky session then you have to make sure that the sessions info are shared between your Tomcat instances otherwise you will lose the sessions details at each switch.

Hope this helps
Fanch

Hi,

Thanks for the reply.

I havent configured my jvmroute in server.xml. I did not understand its advantage.

Is the scenario like this. I have a portal to which i "login".
If that tomcat instance crashes due to some reason then i will have to relogin my portal in the new tomcat instance[ it is also a balanced worker].

can you explain the scenario in detail. As my tomcat is 4.1.18 i do not have any clustering. So how does it help to have sticky sessions.

Regards
Subir S