We have a cluster consisting of 3 websphere application servers, we use memory to memory replication (entire domain topology) to replicate each session in all application servers in the domain, we want the cluster to be able to keep 7000 sessions, should we set Maximum in-memory session count to 7000? or when a session is replicated to another application server, that session is not counted as that server's session and we can set this number to a lower value (for example 2500)?
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2013-01-22T09:27:33Z by gas
Pinned topic session management
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-22T09:27:33Z at 2013-01-22T09:27:33Z by gas
gas 110000E92M888 PostsACCEPTED ANSWER
Re: session management2013-01-22T09:27:33Z in response to EJA3_sara_ahmadiYou should set 7000 on all.
Let assume you have 2000 active sessions on every member, now one of your members fails, then these sessions become active on other members and they will have about 3000 sessions each. If the second server will fail, you will have to be able to handle all 6000 on one (in theory at least :-)) .
Any reason why you'd chosen entire domain instead of single replica? In this case each of your members holds 2/3 currently unneeded sessions (instead of 1/2) and if you add next member it will be 3/4.