PRODUCTS AND SERVICES INDUSTRIES SUPPORT PARTNERS COMMUNITIES ABOUT
   
  Label: cluster
View: Popular Labels | All Labels

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 , more »

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 ...
Automatically manage dynamic cluster membership (Coherence 3.4 User Guide)
Coherence manages cluster membership, automatically adding new servers to the cluster when they start up and automatically detecting their departure when they are shut down or fail. Applications have full access to this information, and can sign up to receive event notifications ...
Clustering (Coherence 3.4 User Guide)
Coherence is built on a fully clustered architecture. Since "clustered" is an overused term in the industry, it is worth stating exactly what it means to say that Coherence is clustered. Coherence is based on a peertopeer clustering protocol, using a conference room model, in which servers ...
Cluster Services Overview (Coherence 3.4 User Guide)
Coherence functionality is based on the concept of cluster services. Each cluster node can participate in (which implies both the ability to provide and to consume) any number of named services. These named services may already exist, which is to say that they may already ...
Cluster your objects and your data (Coherence 3.4 User Guide)
Coherence is an essential ingredient for building reliable, highscale clustered applications. The term clustering refers to the use of more than one server to run an application, usually for reliability and scalability purposes. Coherence provides all of the necessary capabilities for applications ...
Coherence Caching Terminology (Coherence 3.4 User Guide)
several terms which are used to describe the ability of multiple servers to work together to handle additional load or to survive the failure of a particular server. Basic terms Failover Failover refers to the ability of a server to assume the responsibilities of a failed server. For example, "When ...
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 create a cluster-wide named mutex? (Coherence FAQ)
create a clusterwide, named mutex, simply lock a key in a cache with an infinite wait time. Note that a key can be locked even though the key does not actually exist in the cache. This example implements a nonrecursive mutex. String sMutexName = "myNamedMutex ...
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 implement a Clustered Singleton? (Coherence FAQ)
following code example demonstrates how to implement a clustered singleton. import com.tangosol.net.CacheFactory; import com.tangosol.net.NamedCache; / Singleton using cache to back it. (Commented out code is from a singleJVM traditional singleton pattern. New code supports stateless session EJB ...