WildFly HornetQ Message Replication-Based HA Configuration
External
- EAP 6 Administration and Configuration Guide - HornetQ Message Replication - https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/sect-High_Availability.html#HornetQ_Message_Replication
Internal
Overview
For high availability purposes, the live server and the backup server must be installed on two separated physical (or virtual) hosts, provisioned in such a way to minimize the probability of both host failing at the same time.
Configuration
Whether this server is using shared store or not. Default is false.
backup-group-name
This is the unique name which identifies a live/backup pair that should replicate with each other. Example: "pair-A".
check-for-live-server
If a replicated live server should check the current cluster to see if there is already a live server with the same node id. Default is false.
TODO: ?
failover-on-shutdown
Whether this backup server (if it is a backup server) becomes the live server on a normal server shutdown. Default is false.
allow-failback
Whether this server will automatically shutdown if the original live server comes back up. Default is true.
max-saved-replicated-journal-size
The maximum number of backup journals to keep after failback occurs. Specifying this attribute is only necessary if allow-failback is true. Default value is 2, which means that after 2 failbacks the backup server must be restarted in order to be able to replicate journal from live server and become backup again.
Procedure
Active Node Configuration
...
<subsystem xmlns="urn:jboss:domain:messaging:1.4">
<hornetq-server>
<backup>false</backup>
<shared-store>false</shared-store>
<backup-group-name>pair-A</backup-group-name>
<check-for-live-server>true</check-for-live-server>
<failover-on-shutdown>true</failover-on-shutdown>
<persistence-enabled>true</persistence-enabled>
<cluster-user>hq</cluster-user>
<cluster-password>hq123</cluster-password>
...
<connectors>
...
<netty-connector name="backup-node-connector" socket-binding="backup-node-hornetq-binding"/>
</connectors>
...
<cluster-connections>
<cluster-connection name="pair-A-high-availability-cluster">
<address>jms</address>
<connector-ref>netty</connector-ref>
<retry-interval>500</retry-interval>
<use-duplicate-detection>true</use-duplicate-detection>
<forward-when-no-consumers>true</forward-when-no-consumers>
<max-hops>1</max-hops>
<static-connectors>
<connector-ref>backup-node-connector</connector-ref>
</static-connectors>
</cluster-connection>
</cluster-connections>
...
<jms-connection-factories>
...
<connection-factory name="RemoteConnectionFactory">
<ha>true</ha>
<retry-interval>1000</retry-interval>
<retry-interval-multiplier>1.0</retry-interval-multiplier>
<reconnect-attempts>-1</reconnect-attempts>
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
</entries>
</connection-factory>
...
</jms-connection-factories>
</hornetq-server>
</subsystem>
...
<socket-binding-group name="standard-sockets"...>
...
<outbound-socket-binding name="backup-node-hornetq-binding">
<remote-destination host="1.2.3.5" port="5445"/>
</outbound-socket-binding>
</socket-binding-group>
Backup Node Configuration
...
<subsystem xmlns="urn:jboss:domain:messaging:1.4">
<hornetq-server>
<backup>true</backup>
<shared-store>false</shared-store>
<backup-group-name>pair-A</backup-group-name>
<check-for-live-server>true</check-for-live-server>
<failover-on-shutdown>true</failover-on-shutdown>
<persistence-enabled>true</persistence-enabled>
<cluster-user>hq</cluster-user>
<cluster-password>hq123</cluster-password>
...
<connectors>
...
<netty-connector name="active-node-connector" socket-binding="active-node-hornetq-binding"/>
</connectors>
...
<cluster-connections>
<cluster-connection name="pair-A-high-availability-cluster">
<address>jms</address>
<connector-ref>netty</connector-ref>
<retry-interval>500</retry-interval>
<use-duplicate-detection>true</use-duplicate-detection>
<forward-when-no-consumers>true</forward-when-no-consumers>
<max-hops>1</max-hops>
<static-connectors>
<connector-ref>active-node-connector</connector-ref>
</static-connectors>
</cluster-connection>
</cluster-connections>
...
<!--
<jms-connection-factories>
...
</jms-connection-factories>
-->
</hornetq-server>
</subsystem>
...
<socket-binding-group name="standard-sockets"...>
...
<outbound-socket-binding name="active-node-hornetq-binding">
<remote-destination host="1.2.3.4" port="5445"/>
</outbound-socket-binding>
</socket-binding-group>
JMS Connection Factories and JMS Destinations on the Backup Server
A backup HornetQ instance does not need the <jms-connection-factories> and <jms-destinations> sections as any JMS components are created from the shared journal when the backup server becomes live.
Log Output
Active server starting:
00:54:10,313 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=false,journalDirectory=/opt/jboss/standalone/data/messagingjournal,bindingsDirectory=/opt/jboss/standalone/data/messagingbindings,largeMessagesDirectory=/opt/jboss/standalone/data/messaginglargemessages,pagingDirectory=/opt/jboss/standalone/data/messagingpaging) 00:54:17,461 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221013: Using NIO Journal 00:54:19,925 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221007: Server is now live 00:54:19,925 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221001: HornetQ Server version 2.3.25.Final (2.3.x, 123) [5802038e-e5bb-11e5-89d2-3d869d769af8] ...
Stand-by server starting:
Failover to stand-by server: