Bug 1038621

23. Set Up JGroups Interfaces
Rename to "23. JGroups Configuration"

23.1. About JGroups
"JGroups is the underlying group communication library used to connect Red Hat JBoss Data Grid instances. JGroups allows users to bind to an interface type rather than a specific (unknown) IP address."

Remove the second sentence, keep just

"JGroups is the underlying group communication library used to connect Red Hat JBoss Data Grid instances."

Now, 23.2 and 23.3 should both go into section titled
23.2 Configure JGroups interface binding (Remote client-server mode)

Rename "23.2 Configure JGroups Interfaces" -> "23.2.1 Configure Red Hat JBoss Data Grid interfaces"

Remove following text (BEGIN-END) from 23.2.1, as socket binding should be described later in 23.2.2

---BEGIN---
Before JGroups Interface configuration, configure the Red Hat JBoss Data Grid configuration (clustered.xml or standalone.xml depending on the type of deployment) file to a key word rather than a dotted decimal or symbolic IP address as follows:

<socket-binding name="jgroups-udp" ...  interface="site-local"/>

Then, configure the JGroups Interface as follows:
---END---

Instead, place following text below heading 23.2.1

"Red Hat JBoss Data Grid allows users to specify an interface type rather than a specific (unknown) IP address."

Change the "Procedure 23.1. Configure the JGroups Interface" into something more like set of options - it's not a sequence of steps. Also rename it to
"Configure Red Hat JBoss Data Grid interfaces" as this is not JGroups specific.

The configurations excerpts are flawed, and stack upon the previous ones - I'll provide them as separate option each (and fixed). Please, check the correct indentation. Otherwise the text is correct.

1)
<interfaces>
    <interface name="link-local">
        <link-local-address/>
    </interface>
    ...
</interfaces>

2)
<interfaces>
    <interface name="site-local">
        <site-local-address/>
    </interface>
    ...
</interfaces>

3)
<interfaces>
    <interface name="global">
        <any-address/>
    </interface>
    ...
</interfaces>

4)
<interfaces>
    <interface name="non-loopback">
        <not>
	    <loopback />
	</not>
    </interface>
</interfaces>

23.3. Binding Sockets -> 23.2.1 Binding Sockets

"Group interfaces can be used to bind all socket bindings within a given socket binding group or to bind individual sockets."

change to

"Socket bindings provide a named the combination of interface and port.
Sockets may be bound to the interface either individually or using a socket binding group."

new section 23.2.3. (BEGIN-END)

---BEGIN---
23.2.3. Configure JGroups Socket Binding

Each JGroups stack, configured in the JGroups subsystem, uses particular socket binding. Use following to setup the socket binding:

<subsystem xmlns="urn:jboss:domain:jgroups:1.2" default-stack="udp">
    <stack name="udp">
        <transport type="UDP" socket-binding="jgroups-udp">
            ...
        </transport>
        <!-- rest of protocols -->
    </stack>
</subsystem>

Important:
When using UDP as the JGroups transport, the socket binding has to specify both 
regular (unicast) port, multicast address and multicast port.
---END---

Rename "23.4 Configure JGroups for Clustered Modes" -> "23.3. Configure JGroups (Library Mode)"

23.4.1. JGroups Transport Protocols

Remove second and third paragraph, JDG is not based on WildFly and generally this is rather confusing.

In 4th paragraph, change "TCP/IP" to "TCP". Similar in following text: no "TCP/IP", just "TCP".

23.4.1.3. Using the TCPPing Protocol
"As an alternative to using the pre-configured TCP file, which uses TCP/Mping, the TCPPing protocol stack can be added to your configuration and used as the default mechanism. The TCPPing approach contains a static list of the IP address of each member of the cluster in the JGroups configuration file. "

Change this to 

"The pre-configured jgroups-tcp.xml includes the MPING protocol, which uses UDP multicast for discovery. When UDP multicast is not available at all, the MPING protocol, has to be replaced by different mechanism. The recommended alternative is the TCPPING protocol. Configuration of TCPPING contains a static list of IP addresses which should be contacted for node discovery."

23.4.2.1. jgroups-udp.xml
Remove the "minimizes inefficient use of sockets."

23.4.2.2. jgroups-tcp.xml
Remove the "Maximum cluster size for TCP is slightly greater in distribution mode than in replication or invalidation modes."

23.5. Test Multicast Using JGroups
Add this:
"This section shows how to check that your system has properly configured multicasting within the cluster."