Fusion Application Server uses Infinispan to share state between cluster elements, and Infinispan in turn uses JGroups as the transport mechanism for sharing this state. JGroups uses multicast to discover other nodes, and then uses TCP to share state between nodes. Each cluster has a unique cluster ID (set during installation), and nodes do not share state with other nodes unless the cluster IDs match. Nodes only accept discovery requests from nodes with the same cluster ID, but if you have several distinct clusters in the same subnet, you will see warning messages in the log, stating that discovery requests have been rejected because the cluster IDs do not match.
To avoid these warning messages, you can use the following process to set the multicast address and port for JGroups, so that each cluster is restricted to a specific address and port. You will first need to decide which multicast addresses and ports each cluster will use.
To set the multicast address and port for a cluster:
-
Launch the Management Console - see the Starting the Management Console section in the Management Interfaces article.
-
From the top right menu, choose Profiles.
-
From the menu on the left, expand General Configuration section select Socket Binding:
It doesn’t matter which profile you select for this change, as the settings you will change here are not related to a specific profile.
- In the ha-sockets row, click View->:
-
Select jgroups-mping in the Available Socket Bindings section, and click Edit.
-
Expand the Multicast section:
- Edit the Multicast Port or Multicast Address values as required.
If you edit the address, replace the whole string with the new address. For example, to set the address to 230.0.0.10, replace the whole string ${jboss.default.multicast.address:230.0.0.4} with 230.0.0.10.
-
Click Save.
-
In the lb-sockets row, click View->.
-
Repeat the previous steps.
The multicast address and port of jgroups-mping must match on the ha-sockets and lb-sockets.
Comments
0 comments
Please sign in to leave a comment.