JBoss.org Community Documentation

Chapter 19. JBossCache and JGroups Services

19.1. JGroups Configuration
19.2. Common Configuration Properties
19.3. Transport Protocols
19.3.1. UDP configuration
19.3.2. TCP configuration
19.3.3. TUNNEL configuration
19.4. Discovery Protocols
19.4.1. PING
19.4.3. TCPPING
19.4.4. MPING
19.5. Failure Detection Protocols
19.5.1. FD
19.5.2. FD_SOCK
19.5.4. FD versus FD_SOCK
19.6. Reliable Delivery Protocols
19.6.1. UNICAST
19.6.2. NAKACK
19.7. Other Configuration Options
19.7.1. Group Membership
19.7.2. Flow Control
19.7.3. Fragmentation
19.7.4. State Transfer
19.7.5. Distributed Garbage Collection
19.7.6. Merging
19.7.7. Binding JGroups Channels to a particular interface
19.7.8. Isolating JGroups Channels
19.7.9. Changing the Group Name
19.7.10. Changing the multicast address and port
19.7.11. JGroups Troubleshooting
19.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.