Hazelcast Tomcat web session replication

[hazelcast]

Hazelcast Tomcat web session replication

[RubavathiSrinivasan]

on server failover, it creates a new sessionid.
We run three servers.
A http session is created with the HZ session id "HZ87EEE832D65749F5825F497D5D117914", on server1,
If server1 goes down requests are redirected to server2 and a new HZ session is created "HZ740B5BB492CA48B7BFAF12224BDAF1D9"

Why is it creating a new session id? Is there anythig we need to do in config?

[gAmUssA]

@RubavathiSrinivasan please, share your https server (load balancer) details.
Thank you

[RubavathiSrinivasan]

@gAmUssA after added the cookie 'hazelcast.sessionId' and sticky session changes, it works fine now. But we need to maintain two session cookies, JSESSIONID and hazelcast.sessionId, is it possible to achieve session replication using JSESSIONID alone(especially on cluster failover) ? There are no clustered maps for originalsessionid as key and hazelcast.sessionId as value.

[mesutcelik]

JSESSIONID is controlled by web container and created if a new request comes into it. hazelcast.sessionId is used as clusterwide session id so that in case of failover new server figures out what session data is available for the new JSESSIONID.

To answer your question,JSESSIONID only is not sufficient for session replication.

This repository is not right place to discuss this. Can you please continue on Google Groups if you still have questions?

Thanks for using Hazelcast!