Re: HTTPSession Cookie Changed

So far I have only seen this in clusters with session replication and a round robin load balancer (or multiple DNS entries which is basically some sort of round robin load balancing). Sometimes session replication fails and a new session is created on a cluster node. You could use sticky load balancing to reduce the chance of a lost session because of replication. 

Already searched for JBOSS issues regarding lost sessions?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/zyBSwa6mc30J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.