Dave Colasurdo wrote:
Jeff,
Upgraded tomcat, tomcat_ajp and jasper to 5.5.15 and ran the
clustering tests.
The *good* news...
Load balancing, sticky session, session replication and session
failover seem to work using the same deployment plan that was created
for G1.1 w/ TC 5.5.9..
The *bad* news...
*Problem1*
When testing Sticky session, my browser locks unto a particular
cluster member (e.g. node1) due to the nodeid in the cookie. If I kill
node1, the session fails over into node2 and all my session data is
still present. This is good.
The nodeid in the cookie continues to say node1 (this is also true w/
TC 5.5.9 w/ and mod-jk)..
ok, this is probably not desired behavior for a cluster with more than 2
nodes.
For this to work correctly, you need to have the JvmRouteBinderValve
configured in tomcat.
This valve, will rewrite the sessionId to include the new jvmRoute,
node2 in your scenario.
Filip
