You have to use sticky sessions.
Turning on sticky sessions defeats the purpose of load balancing. It keeps a user pinned to one server regardless of load or anything else.
This is a VERY serious bug (in my opinion). I can't seem to find any info of any progress in fixing this bug. I was hoping JBoss offered some kind of work-around or Valve....but I haven't been able to find it.
use tag in your app's web.xml
This will make your app distributed among the available nodes which is actually necessary in replication of your sessions.
Did the tag worked for you?
but, still I see the same prob (with login)
Please let me know if you find any solution/work-around.
Please ignore my previous post...
The issue I'm facing is same as initial post by "sudeepthi" i.e., Problem with Apache loadbalancer, j_security_check and JBoss (in clustered env).
Please let me know if any of you come across any solution/work-around.
I have a similar problem. I don't know the real solution. If anyone knows, please let me know. I am on JBoss 4.2.1.
However, Uncomment following valve in deploy\jboss-web.deployer\server.xml worked.
Sorry forgot to put code tag.
<Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" />