WildFly JGroups Subsystem Configuration: Difference between revisions
Line 72: | Line 72: | ||
3. JGroups code defaults. | 3. JGroups code defaults. | ||
=Configuring a New Protocol Attribute= | =Configuring a New Protocol or Transport Attribute= | ||
A new value for a protocol attribute can be configured with the following syntax: | |||
<pre> | |||
<property name="">301</property> | |||
</pre> | |||
A list of possible configuration attributes can be obtained from <tt>jgroups-defaults.xml</tt> embedded with | |||
=TCP-based Configuration= | =TCP-based Configuration= |
Revision as of 23:18, 29 June 2016
Internal
Relevance
- EAP 6.4
Subjects
Overview
The JGroups stacks are defined within the "jgroups" subsystem:
<subsystem xmlns="urn:jboss:domain:jgroups:1.1" default-stack="udp"> <stack name="udp"> <transport type="UDP" socket-binding="jgroups-udp"/> <protocol type="PING"/> <protocol type="MERGE3"/> <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> <protocol type="FD"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="pbcast.NAKACK"/> <protocol type="UNICAST2"/> <protocol type="pbcast.STABLE"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG2"/> <protocol type="RSVP"/> </stack> <stack name="tcp"> <transport type="TCP" socket-binding="jgroups-tcp"/> <protocol type="MPING" socket-binding="jgroups-mping"/> <protocol type="MERGE2"/> <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> <protocol type="FD"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="pbcast.NAKACK"/> <protocol type="UNICAST2"/> <protocol type="pbcast.STABLE"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG2"/> <protocol type="RSVP"/> </stack> </subsystem>
Subsystem Configuration Schema
Default Values
JGroups stack configuration values are applied from, in this order:
1. standalone*.xml/domain.xml.
2. The ProtocolDefaultsService (implemented by org.jboss.as.clustering.jgroups.subsystem.ProtocolDefaultsService, part of jboss-as-clustering-jgroups-*.jar) which is initialized at startup with values from the file jgroups-defaults.xml embedded in the root of $JBOSS_HOME/modules/system/layers/base/org/jboss/as/clustering/jgroups/main/jboss-as-clustering-jgroups-*.jar or the respective overlay, if the installation was patched.
3. JGroups code defaults.
Configuring a New Protocol or Transport Attribute
A new value for a protocol attribute can be configured with the following syntax:
<property name="">301</property>
A list of possible configuration attributes can be obtained from jgroups-defaults.xml embedded with