Sticky Sessions while using jk2 on apache-jboss
Hi,
I have my application deployed on Jboss-tomcat on 2 linux machines. These instances are standalone and are not aware of each other.
I have my Apache2.0.50 on my win2k desktop. And using the the workers2.prop file mentioned above, i have pointed requests to the apache to the 2 my application deployed on the 2 linux servers.
I am having a session time out issue since the session is not getting carried over to both the linux instances while using the app.
Due to this,the user is asked to log in multiple times.
What is the optimal solution for this?
Is this one: Make my session sticky - ie. once the user hits a particular node (jboss-tomcat) behind apache, he continues to hit the same node.
How do i configure this on my apache?
If this is possible, can apache take care of session failovers (in the event one of my linux servers goes down automatically moves over to the next server without the user having to login)?
I already used worker.lb.sticky_session =JK_TRUE in my workers2.property file, but the login page keeps coming back!
Could some one help me out with this at the earliest?
Thanks and Regards,
Ajith
|