Clustering from a network point of view

For a cluster to work properly, it needs a network where all members can advertise themselves and receive notifications. Despite TCP or UDP network configurations, cluster members need to find each other to be able to exchange information and states.

In JBoss EAP, a cluster is composed of an IP and a port number. These two types of information uniquely identify a cluster on a network.

By default, EAP uses the following configurations:

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> 
    <socket-binding name="management-http" interface="management"
     port="${jboss.management.http.port:9990}"/> 
    <socket-binding name="management-https" interface="management" 
     port="${jboss.management.https.port:9993}"/> 
    <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/> 
    <socket-binding name="http" port="${jboss...