Checked with team about which JGroups values we do support. According to Martin, there shouldn't be any we don't support when talking about attributes of protocols.

However, for the protocols themselves, we don't support AUTH (off the top of his head). Drafting a list of protocols.

The team is talking about recommended values for JGroups attributes. Docs will be cc'd into the conversation once they arrive on agreement about some recommended values to share in docs.

This is no longer included for async docs release for 6.3.0 so I've made the following changes to revert it back to what it was before:

1. Commented out appendix UDP and TCP topics.
2. Removed links from About JGroups Topic
3. Removed support table from JGroups table

For both UDP and TCP:
bind_addr=Null/localhost  -> any non-loopback/set address on specific interface
bind_port=0/52000 -> any free port/set specific port
mcast_port=7600/45688 -> 7600/Same as default
thread_pool.queue_max_size=500/None, thread pool should be disabled -> 500/None, queue should be disabled
oob_thread_pool.max_threads=101/101 or higher based on the load -> 10/100 or higher based on load
oob_thread_pool.queue_max_size=500/100 -> 500/None, queue should be disabled

TCPPING:
forgotten ${port_range}

MPING:
bind_addr: same as for UDP

Under UDP, VERIFY_SUSPECT is twice.

Generally, when the Recommended value is same as JGroups default, use 'Same as default' instead of writing the value second time.

Then, the user needs some guidance, when to use:
TCP/UDP (link to 26.2)
MERGE2/MERGE3 (I think that we should use MERGE3 only, as MERGE2 was deprecated for JGroups 3.5 with JDG 6.4 is using)
PING/TCPPPING/MPING/S3_PING
FD_SOCK/FD_ALL/FD_HOST (+VERIFY_SUSPECT)

If the guidance is stated elsewhere in the docs (as in the 26.2 case or 27 for S3_PING), provide link there.

The fix for this bug is now available on access.redhat.com