WildFly Clustering without Multicast: Difference between revisions
Jump to navigation
Jump to search
(→CLI) |
(→CLI) |
||
Line 58: | Line 58: | ||
/subsystem=jgroups/stack=tcp:remove-protocol(type=MPING) | /subsystem=jgroups/stack=tcp:remove-protocol(type=MPING) | ||
/subsystem=jgroups/stack=tcp:add-protocol(type=TCPPING) | /subsystem=jgroups/stack=tcp:add-protocol(type=TCPPING) | ||
/subsystem=jgroups/stack=tcp/protocol=FD_SOCK/property=:add(value=) | |||
</pre> | </pre> | ||
Note that the operation requires reload (see [[reload]]) | Note that the operation requires reload (see [[reload]]) |
Revision as of 05:05, 24 February 2016
External
- How do I switch clustering to TCP instead of multicast UDP in EAP 6? https://access.redhat.com/solutions/140103
Internal
Procedure
Switch to a "tcp" Default Stack
Manual
Locate the "jgroups" subsystem in standalone.xml or domain.xml relevant profile, and set default-stack value to "tcp":
... <subsystem xmlns="urn:jboss:domain:jgroups:1.1" default-stack="tcp"> ...
CLI
/subsystem=jgroups:write-attribute(name=default-stack,value=tcp)
Note that the operation requires reload, but you should reload the server configuration only after the entire procedure is complete (see reload)
Replace the MPING protocol with TCPPING
Manual
Locate the "tcp" stack inside the "jgroups" subsystem and replace the MPING protocol with TCPPING:
... <stack name="tcp"> <transport type="TCP" socket-binding="jgroups-tcp"/> <protocol type="TCPPING"> <property name="initial_hosts">1.2.3.4[7600],1.2.3.5[7600]</property> <property name="num_initial_members">2</property> <property name="port_range">0</property> <property name="timeout">2000</property> </protocol> <!--<protocol type="MPING" socket-binding="jgroups-mping"/>--> <protocol type="MERGE2"/> ... </stack>
CLI
/subsystem=jgroups/stack=tcp:remove-protocol(type=MPING) /subsystem=jgroups/stack=tcp:add-protocol(type=TCPPING) /subsystem=jgroups/stack=tcp/protocol=FD_SOCK/property=:add(value=)
Note that the operation requires reload (see reload)