Is There A Way To Force All Sessions To Get Replicated Or Be Able To Do A Ripple Start Of The Servers And Not Lose Sessions in Oracle GlassFish Server 3.1.x?
(Doc ID 1564064.1)
Last updated on JUNE 23, 2022
Applies to:Oracle GlassFish Server - Version 3.1.2 and later
Information in this document applies to any platform.
Sometimes when deploying applications to a cluster of servers it is best to do a ripple start of the servers. In Glassfish 2.x, server instance 1 can be shut down and restarted, and then if an application running on instance 1 is accessed, every user's session information gets replicated across to instance 1. At that point instance 2 can be stopped and then started and session data will not be lost. But with Glassfish 3.1, after restarting instance 1 and accessing an application on it, it only pulls that particular user session across to instance 1 and therefore, if instance 2 is restarted, all other users will lose their session. Is there a way to force all sessions to get replicated or be able to do a ripple start of the servers and not lose sessions?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document