Hi all,
we tried to switch with a clusterable webapp from Tomcat 5.0
to Tomcat 5.5 and ran into problems with the primary session
indication by the ReplicationValve. We have a cluster with two
nodes (let's call them 'A' and 'B'). A sticky session is created
at node A and is reported there as
Hey Michael,
yes that is true here my fix:
ReplicationValve:
protected void resetReplicationRequest(Request request, boolean
isCrossContext) {
Session contextSession = request.getSessionInternal(false);
if(contextSession != null contextSession instanceof
Hi Peter!
Peter Rossbach wrote:
yes that is true here my fix:
[...]
Can you please test this, then I can commit the change.
Yes, it works! Many thanks! :)
Tipp:
That your client/browser also know that B is forever the primary use
JvmRouteBinderValve. That helps very much for longer
