All content with label cluster+update-after-forums-move.
Related Labels: heap , failover , coherence-web , proxy , production-environment , listeners , reliability , availability , c-w-archive , mutex , service , sessions , failback , performance , optimistic , testing , faq-coherence-web , operating-system , session-cache-config , mbeans , replication , local , mutext , hardware , manageability , faq-code-examples , security , events , installation , best-practices , session-management , servletcontext , backing-map , core-concept , scalability , network , serviceability , httpsessioncontext , death-detection , invocation , example , multicast , faq-config , member , glossary , federation , distributed , singleton , load-balancing more » ( - cluster , - update-after-forums-move )

Advanced Session Scoping (Coherence 3.4 User Guide) Sometimes you may want to explicitly prevent HTTP session data from being shared by different Java EE applications that participate in the same Coherence cluster. For example, say you have two applications {{HRPortal}} and {{InWeb}} that share cached ...

How do I prevent session data from being shared by different apps? (Coherence FAQ) Sometimes you may want to explicitly prevent HTTP session data from being shared by different Java EE applications that participate in the same Coherence cluster. For example, say you have two applications {{HRPortal}} and {{InWeb}} that share cached ...