Skip to main content

JBoss Fuse/A-MQ - Easy way to achieve fault tolerant messaging Part 1

Following some of the questions I got from the people during the enablement in APAC, one of the question I get is how to do achieve fault tolerant, I believe there are already many works done out there that talks very technical and search deeply in this area.

But as always, I am going to show few simple steps to achieving fault tolerant messaging with A-MQ.

The simplest way to make your messaging system fault tolerant is to make your broker into Master/Slave group. Therefore when one broker goes down a backup server will takeover.


So we can now ensure our broker will always be up and running, Fuse does a beautiful job of detecting and switching.

There are 2 ways to spin up an the broker, one with the beautiful management GUI with Fuse, or the old hardcore command line.

Please make sure you have installed Fuse and boot up the Fabric before you begin.
Logon to JBoss Fuse management Console, under Runtime -> MQ-> +Broker






Add group, broker name and choose MasterSlave kind, then click on create broker, after that, you broker diagram should appear in the list, click on the red triangle in the middle.








Create the container by giving a name to it.






And you will see 2 containers with one actively listens to the client and one standby container.


Now, because the way we spin up our message broker, an port will automatically assigned to each connector to the port, to avoid conflict, it is going to assign ports that is not in use. But for the clients to connect to the broker, you probably want your program to detect the ports of the broker automatically. With A-MQ it has a convenient and easy way of detecting with Zoo Keeper registry. I will be showing it through a camel route.

The configuration is really easy, instead of setting your messaging address to a specific address and port like below:

  <bean id="jmsConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
      <property name="brokerURL" value="tcp://localhost:61616"/>
      <property name="userName" value="admin"/>
      <property name="password" value="admin"/>
  </bean>

or using the failover that must point out the address before hand (static), where the client must know where every single one of


  <bean id="jmsConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
      <property name="brokerURL" value="failover:(tcp://localhost:61616,tcp://localhost:61617)"/>
      <property name="userName" value="admin"/>
      <property name="password" value="admin"/>
  </bean>

But, we can always use the fabric discovery protocol to find out all the broker registry. the only configuration that will need is to add the discovery configurations to the broker URL.

  <bean id="jmsConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
      <property name="brokerURL" value="discovery:(fabric://blogdemo)"/>
      <property name="userName" value="admin"/>
      <property name="password" value="admin"/>
  </bean>

As for library dependency, there are a few artifacts you will need to add to your project other then messaging libraries, are fabric related artifacts like, fabric-groups, fabric-zookeeper and the osgi ones.  So to do that, make sure you add the following dependency into your pom.xml

    
    
      org.apache.activemq
      activemq-camel
      5.9.0.redhat-610379
    
    
      org.apache.activemq
      activemq-pool
      5.9.0.redhat-610379
    
    
      org.apache.activemq
      activemq-osgi
      5.9.0.redhat-610379
    
    
    
    
     org.jboss.amq
     mq-fabric
     6.1.0.redhat-379
 
 
     io.fabric8
     fabric-groups
     1.0.0.redhat-379
 
 
     io.fabric8
     fabric-zookeeper
     1.0.0.redhat-379
 
 
 
 
     org.osgi
     org.osgi.core
     5.0.0
 
 
     org.osgi
     org.osgi.compendium
     5.0.0
 

And another important configuration, because we are going to take advantage of the Zoo Keeper registry, so we must tell the application where to lookup the registry and add the zoo keeper password to the pom.xml making sure we were authorized to lookup into the registry, not just some random application happens to float around.

  
    <!-...... -->
    localhost:2181            
    admin           
  

And the rest is just the same for a normal messaging application.

In my demo, I had 2 route,

1st route will send a message to the broker every 5 mins,









2nd route read and then log the message










When starting the demo, you can see the messages are starting to send into the active broker,



Once we turn off the container, the standby container will takeover,


and the client application will automatically switch to the new active broker.










Next part of the topic, I will do a live video, and publish the code on github. (Part 2)

Comments

Popular posts from this blog

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

jboss-devstudio-9.0.0.GA-installer-eap.jar
double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.


And select JBoss Fuse Development for the plugin,


Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.



And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

RHTE - Supercharge your integration services

Red Hat Tech Exchange has taken place in Vietnam, Ho Chi Minh city two weeks ago, it is a great event held by Red Hat in Asia Pacific Region. It is open to all Red Hat partners who are interested in learning what Red Hat is doing recently, see what the trend of the open source world, basically it is a great event to share your knowledge and experience, to meet other enthusiastic people.

I am very fortunate to talk in this great event, to talk about the things I have been working on and even discuss it with many. Also got lots of great ideas too. So here are the slide.

My first talk was with Thomas Qvarnström about how to handle large size data in JBoss Fuse and how JBoss Data Grid can help in the situation.

Here is the agenda of the talk, we will be talk about this in the up coming webinar on 24th Sept.

Integration often involves storing, retrieving, and transforming data. Using a traditional database in your integration is likely to becomes a bottleneck that is expensive and hard to …