WildFly HornetQ Cluster Connection Configuration: Difference between revisions
Jump to navigation
Jump to search
Line 35: | Line 35: | ||
==<tt>address</tt>== | ==<tt>address</tt>== | ||
Each cluster connection only applies to messages sent to an [[WildFly_HornetQ-Based_Messaging_Subsystem_Concepts#Address_2|address]] that starts with this value. The address can be any value and you can have many cluster connections with different values of addresses, simultaneously balancing messages for those addresses, potentially to different clusters of servers. This does not use wild card matching | |||
==<tt>max-hops</tt>== | ==<tt>max-hops</tt>== | ||
In [[WildFly_HornetQ-Based_Messaging_Subsystem_Concepts#Symmetric_Cluster|symmetric clusters]], <tt>max-hops</tt> must be set to 1. | In [[WildFly_HornetQ-Based_Messaging_Subsystem_Concepts#Symmetric_Cluster|symmetric clusters]], <tt>max-hops</tt> must be set to 1. |
Revision as of 00:45, 14 May 2016
Internal
Overview
A cluster connections represents an unidirectional communication channel between nodes. More details about the cluster connection concepts are available here: Cluster Connection Concepts. It is configured as follows:
<subsystem xmlns="urn:jboss:domain:messaging:1.4"> <hornetq-server name="active-hq-node"> ... <cluster-connections> <cluster-connection name="load-balancing-to-lb2"> <address>jms</address> <connector-ref>netty-inbound</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> load-balancing-node-lb2 </connector-ref> </static-connectors> </cluster-connection> </cluster-connections> ... </hornetq-server> </subsystem>
Configuration Elements
address
Each cluster connection only applies to messages sent to an address that starts with this value. The address can be any value and you can have many cluster connections with different values of addresses, simultaneously balancing messages for those addresses, potentially to different clusters of servers. This does not use wild card matching
max-hops
In symmetric clusters, max-hops must be set to 1.