Recently, I was involved into WebSphere Portal session management with WXS(stand-alone). I was going through the following article on IBM site and bit surprise to know that WXS just replicates/copies session from WebSphere portal JVM to WXS grid. I was thinking that local JVM doesn't store any session object after offloading it to WXS grid. But I guess I was wrong.
Here is a stanza which clarifies this.
"After HTTP session management is initiated, WebSphere eXtreme Scale replicates every new session created on WebSphere Application Server into the grid container, once for every predefined session replication interval. The WebSphere eXtreme Scale container is located on another server instance where all of the other cluster members can share and obtain the session data. Should an application server go down, the other application servers can still obtain the latest session data to implement HTTP session failover.
You can find below URL for the document.
If this is the way it is implemented then how would the local JVM heap be freed to improve the performance of the application?
Any thoughts on this will be appreciable.