Hi,
This is a bit of documentation from the Load balancing page of the
Apache site.
sticky_session specifies whether requests with SESSION
ID's should be routed back to the same Tomcat worker. You
can set sticky_session to False when Tomcat is using a
Session Manager which can persist session data across
multiple instances of Tomcat. By default sticky_session
is set to True.
I tired to set the sticky_session value as false, and I was under the
impression that Tomcat has a session manager which can persist session
data across the multiple instances in cluster. But when i set it to
false, the requests are being served by different servers in the
cluster for the same session... That is the session is no longer
sticky. But when this happens sometimes the session replication is
going wrong.
Please make this point clear for me .
Regards,
Shiby
---------------------------------------------------------------------
To start a new topic, e-mail: [email protected]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
