jboss wildfly 8.2 jgroups multicast clustering test

Document ID : KB000122792
Last Modified Date : 10/12/2018
Show Technical Document Details
If you are are having an issues whereby saving IDM UI objects on one server in a clustered environment does not show up in the other server within the cluster.  Then you maybe facing a clustering issue, Most times when this does not work, it usually comes down to Network or configuration

Here is a sample file for you to test configuration against:

IDM manages different cache queue for admin task and role, once changes are made in task/roles while task submission, node which is executing this task will send notification to all clustered nodes to flush their respective queues. 

In this case, all other nodes will fetch data from database instead of cache and must be having updated content (roles/task definition) 

Test Multicast Using JGroups

1) Run the Multicast Server on Node One

Run the following command on the command line terminal for the first node:
java -cp jgroups.jar org.jgroups.tests.McastReceiverTest -mcast_addr -port 5555 -bind_addr $YOUR_BIND_ADDRESS

2) Run the Multicast Server on Node Two

Run the following command on the command line terminal for the second node:
java -cp jgroups.jar org.jgroups.tests.McastSenderTest -mcast_addr -port 5555 -bind_addr $YOUR_BIND_ADDRESS
For my server I had to change the jar file: 
wildfly-8.2.1_home\wildfly-8.2.1.Final\modules\system\layers\base\org\jgroups\main>java -cp jgroups-3.4.5.Final.jar org.jgroups.tests.McastReceiverTest -mcast_addr -port 5555 -bind_addr $YOUR_BIND_ADDRESS

3)Transmit Information Packets

Enter information on instance for node two (the node sending packets) and press enter to send the information.

4) View Receives Information Packets

View the information received on the node one instance. The information entered in the previous step should appear here.

5) Confirm Information Transfer

Repeat steps 3 and 4 to confirm all transmitted information is received without dropped packets.

6)Repeat Test for Other Instances

Repeat steps 1 to 4 for each combination of sender and receiver. Repeating the test identifies other instances that are incorrectly configured.