Chapter 7. JBossCache and JGroups Services

Chapter 7. JBossCache and JGroups Services

7.1. JGroups Configuration
7.2. Common Configuration Properties
7.3. Transport Protocols
7.3.1. UDP configuration
7.3.2. TCP configuration
7.3.3. TUNNEL configuration
7.4. Discovery Protocols
7.4.1. PING
7.4.2. TCPGOSSIP
7.4.3. TCPPING
7.4.4. MPING
7.5. Failure Detection Protocols
7.5.1. FD
7.5.2. FD_SOCK
7.5.3. VERIFY_SUSPECT
7.5.4. FD versus FD_SOCK
7.6. Reliable Delivery Protocols
7.6.1. UNICAST
7.6.2. NAKACK
7.7. Other Configuration Options
7.7.1. Group Membership
7.7.2. Flow Control
7.7.3. Fragmentation
7.7.4. State Transfer
7.7.5. Distributed Garbage Collection
7.7.6. Merging
7.7.7. Binding JGroups Channels to a particular interface
7.7.8. Isolating JGroups Channels
7.7.9. Changing the Group Name
7.7.10. Changing the multicast address and port
7.7.11. JGroups Troubleshooting
7.7.12. Causes of missing heartbeats in FD

JGroups and JBossCache provide the underlying communication, node replication and caching services, for JBoss AS clusters. Those services are configured as MBeans. There is a set of JBossCache and JGroups MBeans for each type of clustering applications (e.g., the Stateful Session EJBs, HTTP session replication etc.).

The JBoss AS ships with a reasonable set of default JGroups and JBossCache MBean configurations. Most applications just work out of the box with the default MBean configurations. You only need to tweak them when you are deploying an application that has special network or performance requirements.