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"/>

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"/>

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"/>

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


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.

    <!-...... -->

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)


Popular posts from this blog

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.



JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。


Connection Pool 最少會存留的connection 數量


Connection Pool 最多可以開啓的 connection 數量


事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。

My 2cents on the future of Integration - With Service Mesh/Istio and Serverless/KNative

It's been a year and half since I blogged about "Agile Integration architecture" (Gosh, time just flies). With the "microservices" and "cloud-native" hype, I was especially curious on how all these new concept and technology affect us on how to architect the integration systems. If you ever pay close attention to all the latest and greatest news from the Kubernetes community, I am sure you will hear a lot about the new "Service Mesh". And rumor has it that this is how integration can/should be done in cloud native world, but, is that so? Anyone who has ever worked on an integration project would tell you, it's a LOT more COMPLEX and can get worst overtime. I did a talk with Christian Posta in Red Hat Tech Exchange coming from a more comprehensive view of how different Red Hat technologies are applied under different patterns when building integration solutions. In fact he also did a great blog about it.

Since then, another topics has be…

Red Hat Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…