JBoss.org Community Documentation

Chapter 20. JBossCache and JGroups Services

20.1. JGroups Configuration
20.2. Common Configuration Properties
20.3. Transport Protocols
20.3.1. UDP configuration
20.3.2. TCP configuration
20.3.3. TUNNEL configuration
20.4. Discovery Protocols
20.4.1. PING
20.4.2. TCPGOSSIP
20.4.3. TCPPING
20.4.4. MPING
20.5. Failure Detection Protocols
20.5.1. FD
20.5.2. FD_SOCK
20.5.3. VERIFY_SUSPECT
20.5.4. FD versus FD_SOCK
20.6. Reliable Delivery Protocols
20.6.1. UNICAST
20.6.2. NAKACK
20.7. Other Configuration Options
20.7.1. Group Membership
20.7.2. Flow Control
20.7.3. Fragmentation
20.7.4. State Transfer
20.7.5. Distributed Garbage Collection
20.7.6. Merging
20.7.7. Binding JGroups Channels to a particular interface
20.7.8. Isolating JGroups Channels
20.7.9. Changing the Group Name
20.7.10. Changing the multicast address and port
20.7.11. JGroups Troubleshooting
20.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.