The failover protocol provides a simple mechanism for clients to failover to a secondary broker endpoint if the primary connection fails. The failover protocol does not require that the brokers be configured as a network of brokers. However, when paired with a network of brokers it can be configured to use dynamic failover locations.
The failover protocol facilitates quick 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 endpoints. 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.
For true high-availability and failover capabilities, you will need to set up your brokers in a network of brokers or a master/slave cluster. See Clustering Guide.
The failover transport allows you to set up failover in one of two ways:
 |  | |
 |
