Infinispan provides a very wide configuration of the network too. The network configuration is a very important part in a cluster. Network environments can be very complex depending on the requested security level. JGroups is the product delegated by Infinispan to represent the low-level configuration network.

With JGroups, for example, we can decide what network protocol is used to send the messages of the replication. This is how the network is configured in the standalone-ha.xml descriptor file of WildFly:

<subsystem xmlns="urn:jboss:domain:jgroups:4.0">
 <channels default="ee">
    <channel name="ee" stack="udp"/>
 </channels>
 <stacks>
    <stack name="udp">
       <transport type="UDP" socket-binding="jgroups-udp"/>
       <protocol type="PING"/>
       <protocol type="MERGE3"/>
       <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/>
       ...
    </stack>

The following is the configuration for the TCP protocol:

   <stack name="tcp">
       <transport type="TCP" socket-binding="jgroups-tcp"/>
       <protocol type="MPING" socket-binding="jgroups-mping"/>
       <protocol type="MERGE3"/>
       <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
       <protocol type="FD"/>
       ...
   </stack>
 </stacks>

In these configurations, we enabled the protocols that must be used to replicate the data. All parts of the TCP and UDP can be configured in JGroups.