|
All content with label faq-coherence-web+cluster.
Related Labels:
heap
, failover
, split
, coherence-web
, proxy
, production-environment
, listeners
, reliability
, traditional
, availability
, c-w-archive
, mutex
, service
, sessions
, failback
, performance
, testing
, optimistic
, operating-system
,
session-cache-config
, j2ee
, java-ee
, mbeans
, replication
, mutext
, local
, hardware
, manageability
, faq-code-examples
, security
, events
, installation
, best-practices
, web
, monolithic
, installer
, session-management
, servletcontext
, libraries
, backing-map
, core-concept
, network
, scalability
, serviceability
, httpsessioncontext
, death-detection
, invocation
, example
, faq-config
, multicast
, federation
, glossary
, member
, distributed
, update-after-forums-move
, singleton
, deploy
, load-balancing
more »
( - faq-coherence-web
, - cluster
)
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 cluster the ServletContext
(Coherence FAQ)
Servlet Specification version 2.4 states in section SRV.3.2: {{In cases where the container is distributed over many virtual machines, a Web application will have an instance of the ServletContext for each JVM.}} The specification further clarifies the distributed scope of ServletContext attributes ...
|
How do I enable HttpSessionContext
(Coherence FAQ)
Servlet Specification version 2.4 states in section SRV.15.1.12: {{public interface HttpSessionContext}} {{Deprecated. As of Java(tm) Servlet API 2.1 for security reasons, with no replacement. This interface will be removed in a future version of this API.}} CoherenceWeb is fully compliant to the Servlet Specification, and as a result ...
|
How do I prevent cluster-replication of certain session attributes?
(Coherence FAQ)
Disabling clustering for session attributes presumes the presence of a sticky load balancer (as the nonclustered attributes will be visible only to requests executing locally within that JVM). # Implement the interface {{HttpSessionCollection.SessionDistributionController}} (in package {{com.tangosol.coherence.servlet}}, in the {{coherenceweb.jar}} found in {{webInstaller.jar}}). The specific method of interest is {{isSessionAttributeDistributed ...
|
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 ...
|
|
|
