As announced this is the last post of our series about clustering of the Redhat EAP 6 and JBoss AS 7. The other posts of this series were
- Clustering in JBoss AS7/EAP 6
- Managing cluster nodes in domain mode of JBoss AS 7 / EAP 6
- Scalable HA Clustering with JBoss AS 7 / EAP 6
- Load-balancing and failover of remote EJB clients in EAP6 and JBoss AS7
- Clustering of the messaging subsystem HornetQ in JBoss AS7 and EAP 6
This post will dig deeper into the clustering mechanisms of the EAP 6 and JBoss AS 7. We will show different solutions to multicast problems you will get in most cloud networks as well as some other networks. Infinispan uses JGroups to do its cluster communication. Cluster communication here means multiple things: finding other cluster nodes, providing a reliable transfer, implementing multicast communication even if there is no IP multicast available, identifying dead cluster nodes and a little bit more. In fact JGroups is able to do a lot more but Infinispan does not need all of the opportunities JGroups offers. The upcoming HornetQ version 2.3 which will be included in the EAP 6.1 will use JGroups for server discovery too. This post will explain the basic principles of JGroups and how to configure it in different network setups, especially most cloud networks.
You must be logged in to post a comment.