The failover protocol is primarily used by clients to facilitate recovery from network failures. When a recoverable network error occurs the protocol catches the error and automatically attempts to reestablish the JMS connection to an alternate broker endpoint without the need to recreate all of the JMS objects associated with the JMS connection. The failover URI is composed of one or more URIs that represent different broker transport connectors. By default, the protocol randomly chooses a URI from the list and attempts to establish a network connection to it. If it does not succeed, or if it subsequently fails, a new network connection is established to one of the other URIs in the list.
Brokers in a network of brokers can be configured to dynamically update their clients' failover lists. The brokers inform their clients about the other brokers in the network so that in the event of a failure the clients know how to connect to a running broker. The brokers update their clients as new brokers join and leave the network.
For more information about configuring a client to use the failover protocol see Failover Protocol in Broker Client Connectivity Guide.
Brokers should never use the failover protocol when configuring its transport connectors. The failover protocol does not support listening for incoming connections.
In general, brokers should not use the failover protocol when configuring its network connectors. The failover protocol's reconnect logic cannot recreate the network bridge between two brokers. It interferes with the network connectors reconnect logic which is required to rebuild dropped network bridges.
The one case where you want to use the failover protocol in a network connector is when you are attempting to create a network of brokers that includes a master/slave cluster. See Fault Tolerant Broker Network for more information.
Configuring a broker to participate in dynamic failover requires two things:
The broker must be configured to participate in a network of brokers that can be available for failovers.
See Broker Networks for information about setting up a network of brokers.
The broker's transport connector must set the failover properties needed to update its consumers.
Table 1.1 shows the broker properties
that configure a failover cluster. These properties are exposed as attributes on the
transportConnector element.
Table 1.1. Transport Connector Failover Properties
![[Note]](imagesdb/note.gif) | Note |
|---|---|
The update and rebalance features should only be enabled, only if the clients that connect to the broker cluster use Fuse Message Broker 5.4.0 or later. These features are incompatible with clients older than version 5.4.0. |
Example 1.1 shows the configuration for a broker that participates in dynamic failover.
Example 1.1. Broker for Dynamic Failover
<beans ... > <broker> ... <networkConnectors><networkConnector uri="multicast://default" /> </networkConnectors> ... <transportConnectors> <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"
discoveryUri="multicast://default"
updateClusterClients="true"
updateClusterFilter="*A*,*B*" /> </transportConnectors> ... </broker> </beans>
The configuration in Example 1.1 does the following:
Creates a network connector that connects to any discoverable broker that uses the multicast transport. | ||||
Makes the broker discoverable by other brokers over the multicast protocol. | ||||
Makes the broker update the list of available brokers for clients that connect using the failover protocol.
| ||||
Creates a filter so that only those brokers whose names start with the letter
|
Example 1.2 shows the URI for a client that uses the failover protocol to connect to the broker and its cluster.
Example 1.2. Failover URI for Connecting to a Failover Cluster
failover://(tcp://0.0.0.0:61616)?initialReconnectDelay=100
 |  |  |
 |
