|
All content with label cluster.
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
, best-practices
, session-management
, servletcontext
, backing-map
, core-concept
, scalability
, network
, serviceability
, httpsessioncontext
, death-detection
, invocation
, example
, multicast
, faq-config
, member
, glossary
, federation
, distributed
, update-after-forums-move
, singleton
, load-balancing
more »
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 ...
|
How to Manage Custom MBeans Within the Coherence Cluster
(Coherence 3.4 User Guide)
addition to How to Manage Coherence Using JMX, Coherence http://www.tangosol.com/coherence.jsp provides the ability to manage and monitor "custom MBeans" (i.e. applicationlevel MBeans) within the Coherence JMX Management and Monitoring framework. This allows you to manage and/or monitor any ...
|
Production Checklist
(Coherence 3.4 User Guide)
Deploying Coherence in a production environment is very different from using Coherence in a development environment. Development environments do not reflect the challenges of a production environment. Coherence tends to be so simple to use in development that developers do not take the necessary planning steps ...
|
Session Management for Clustered Applications
(Coherence 3.4 User Guide)
CoherenceWeb content has been moved and consolidated under the CoherenceWeb Session Management Module page
|
What benefits can be realized in a single-server Coherence installation?
(Coherence FAQ)
While most Coherence installations are deployed in clusters ranging from two to 100 servers, there are many advantages to be gained even in singleserver environments, whether running on a commodity quadprocessor box or a massive partitioned SMP server. This section contains the following information ...
|
|
|
