tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: Session Replication in Cluster
Date Fri, 03 Apr 2009 22:30:50 GMT
Roy McMorran wrote:
> János Löbb wrote:
>> If You look the >>values<< created by the session earlier with
>> ...node1, than You will see the same values after fail over with
>> ...node2.  A new session would not know about them.
>> To verify it You can use the supplied SessionExmaple webapp.
> OK, trying that.
> So, using an example webapp (see:
> (which just uses session.getID() )
> ...should it return *just* the session ID part, or the concatenation of
> the session ID and the jvmRoute?
> Here's what I see:
> Before failover:
> This is the session id FEBA6A8127A69079C79B7A641158CE20.itchy
> This is an existing session
> After failover:
> This is the session id FEBA6A8127A69079C79B7A641158CE20.scratchy
> This is an existing session

Which is 100% correct and expected behaviour. The session ID *has* to
change as the last part, the route, is used by the load balancer to
maintain session stickiness. The contents of both of those sessions will
be identical.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message