Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
This documentation is for WSO2 Message Broker version 3.2.0. For the latest documentation, see the documentation for WSO2 Enterprise Integrator.
Skip to end of metadata
Go to start of metadata

High availability is an important aspect associated with any server implementation that ensures a certain degree of operational continuity when unplanned downtime events impact parts of a system. JMS 1.1 does not provide this; instead, most of the time it is vendor specific.

The idea behind failover is stopping a single-point-of-failure in a system. As the broker is the middle man storing and forwarding the messages, if that server goes down, the entire message flow of the system will go down no matter what other servers and functions are involved. In order to make a robust messaging system, it is mandatory to have a failover mechanism.

In order to achieve this, a few instances of message broker servers are set up and running in the system, while the system (generally) uses one broker. If that broker goes down, it automatically switches to the second broker and continues messaging. If the second broker fails, it will try the next one and so on. Thus, the whole system will not have any downtime.

This page covers the following topics:

Failover with WSO2 Message Broker and WSO2 ESB

Follow the instructions below to set up a failover mechanism using MB and ESB:

Setting up MB instances in a single machine

  1. Download the latest version of MB and extract it into a folder. 
  2. Make an exact copy of MB in three different locations and rename them as MB1, MB2 and MB3. Those will be the 3 separate MB instances. 
  3. Navigate to MB1/repository/conf/carbon.xml and define an offset of 1.

    <Ports>
    <!-- Ports offset. This entry will set the value of the ports defined below to
     the define value + Offset.
     e.g. Offset=2 and HTTPS port=9443 will set the effective HTTPS port to 9445
     -->
     <Offset>1</Offset>
  4. Navigate to MB2/repository/conf/carbon.xml and define an offset of 2. 
  5. Navigate to MB3/repository/conf/carbon.xml and define an offset of 3. 
  6. The 3 MB instances are ready. Start each instance of MB by running one of the following commands:
    • <MB_HOME>/bin/wso2server.sh (on Linux) 
    • <MB_HOME>/bin/wso2server.bat (on Windows)
  7. The MB instances will start on ports 5673, 5674 and 5675 respectively.

Setting up MB instances in different machines

  1. Download the latest version of MB and extract it into a folder.
  2. Make an exact copy of that folder in three separate machines. Let's assume MB1 is in the machine with IP1, MB2 in the machine with IP2 and MB3 in the machine with IP3.
  3. Start all the above instances by running one of the following commands:
    • <MB_HOME>/bin/wso2server.sh (on Linux) 
    • <MB_HOME>/bin/wso2server.bat (on Windows) 
    All severs will start with port offset 0, which is 5672.

Setting up a WSO2 ESB instance

  1. Start ESB in the default port (port offset 0). This is possible if you used the single machine setup above, as those servers were started with different port offsets. If you are using different machines, use another machine to start WSO2 ESB. Instructions can be found in Configure with WSO2 Message Broker.

    It is not possible to start multiple WSO2 products with their default configurations simultaneously in the same environment. Since all WSO2 products use the same port in their default configuration, there will be port conflicts.

  2. There is only a single difference to enable failover across the three brokers we have setup. That is when specifying the following:

    connectionfactory.ConnectionFactory
    
    connectionfactory.QueueConnectionFactory
    
    connectionfactory.TopicConnectionFactory

    For example, if you hope to use a single machine MB setup as described above,

    connectionfactory.QueueConnectionFactory = amqp://admin:admin@clientID/carbon?failover='roundrobin'&cyclecount='2'&brokerlist='tcp://localhost:5673? retries='5'&connectdelay='30000';tcp://localhost:5674?retries='5'&connectdelay='30000';tcp://localhost:5675?retries='5'&connectdelay='30000''

    If you hope to use the broker setup made across several machines as described above,

    connectionfactory.QueueConnectionFactory = amqp://admin:admin@clientID/carbon?failover='roundrobin'&cyclecount='2'&brokerlist='tcp://IP1:5672?retries='5'&connectdelay='30000';tcp://IP2:5672?retries='5'&connectdelay='30000';tcp://IP3:5672?retries='5'&connectdelay='30000''

     The parameters used above are described in detail below:

    Brokerlist option
    brokerlist='<broker url>[;<broker url>]'

    The broker list defines the various brokers that can be used for this connection. A minimum of one broker URL is required. Additional URLs are semi-colon(';') delimited.

    Broker URL format


    <transport>://<host>[:<port>][?<option>='<value>'[&<option>='<value>']]
    OptionDefaultDescription
    retries1The number of times to retry connection to this Broker
    sslfalseUse ssl on the connection
    connecttimeout30000How long in (milliseconds) to wait for the connection to succeed
    connectdelaynoneHow long in (milliseconds) to wait before attempting to reconnect
    Brokerlist failover option


    failover='<method>[?<options>]'
    MethodDescription
    singlebrokerThis will only use the first broker in the list.
    roundrobinThis method tries each broker in turn.
    nofailover[New in 0.5] This method disables all retry and failover logic.
    onetimeThis method ensures that XA transactions do not failover from one node another. That is, if the connection fails before all messages are committed to the broker node, the XA transaction will be canceled. The client will then reconnect to the next available broker in the list and resend all the messages from the beginning. See Handling Distributed Transactions for more information

    The current default is to use the singlebroker method when only one broker is present, and the roundrobin method with multiple brokers. The method value in the URL may also be any valid class on the classpath that implements the FailoverMethod interface.
    Options
    OptionDefaultDescription
    cyclecount1The number of times to loop through the list of available brokers before failure.

Testing the setup

When sending messages to a queue (you can configure SOAP UI to send messages continuously one after the other) using the setup described above, kill MB1. You will notice that failover happens at ESB to the second broker i.e MB2. The logs at the ESB side will indicate that failover occurred. 

If there were any previous messages at MB1, they will not be delivered. 

Usually, the solution for that (and many other problems) is broker clustering. For information on the advantages of clustering and WSO2 Message Broker's support on clustering, see Clustering Message Broker
  • No labels