https://issues.apache.org/bugzilla/show_bug.cgi?id=47510
Barry <bmo...@systemax.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #3 from Barry <bmo...@systemax.com> 2009-11-13 07:02:39 UTC ---
We are having the same problem. We have 4 JBoss 4.2.3 servers in a cluster
using sticky session but no session replication.
Here is the scenario. If the first request gets routed to node1, the sessionid
will end in ".node1" and all requests will go back to that node. Let's say
node1 goes down and the next request gets sent to node2. Since the session is
not on node2, a new session is created. The problem is that the same session
id, the one ending in ".node1" is reused instead of a whole new session id
ending in ".node2" being created.
There are 2 problems with this:
1) There are still 3 other JBoss servers running. All requests from the same
browser using a session id ending in ".node1" will go to random JBoss servers
(no more sticky sessions). This pretty much renders the app useless.
2) When node1 comes back up, the user again is switched back to node1 and
remains there as sticky sessions kicks in.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
