Skip to main content

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

So here is the step by step video to create Failover Client I promise last time.
Before you begin, please make sure you have created the Master/Slave broker beforehand.
Here are the videos:
  • Create Master/Slave Broker
  • Create Client Camel Application

You can find my sample code in github:

Before begin, there are some setups you need to do,
Download JBoss Fuse from

Add fabric server passwords for Maven Plugin to your ~/.m2/settings.xml file the fabric server's user and password so that the maven plugin can login to the fabric.


There are 2 ways to tackle this example, First is to everything manually, create a Master/Slave Broker, build the client Camel Application from scratch and then deploy them onto Fuse. Second way is to everything install and configured and just to play with it.

So, in side my github project, you will find 2 shell scripts

    • This is an simple installation, it basically just install the Fuse and setup the fabric for you, with this setting, you will need to follow along the 2 videos or the instructions from last blog (Part1) and find all the related code here
    • This shell will install everything for you. Including setting up the broker, creating a container, and then deploy the camel application on to Fuse container. 

Have fun with this demo, and please, if you are a window user, feel free to add the window .bat file and contribute back! Thanks!

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


Netuh said…
Hello Christina,

It's Waldemar again. I'm having some problems to execute this example. I tried to download it from github and to execute the blueprint.xml as "local camel context (without test)" as showed in the demo video. It does not run (as presented in the video) and I got the following error message:
java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but interface was expected
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Then I tried to deploy it in a Jboss fuse that was running locally. And I got a failure in building with the following error message:
[ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:1.2.0.redhat-046:deploy (default-cli) on project failoverdemo: Execution default-cli of goal io.fabric8:fabric8-maven-plugin:1.2.0.redhat-046:deploy failed: Unable to load the mojo 'deploy' in the plugin 'io.fabric8:fabric8-maven-plugin:1.2.0.redhat-046' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: io/fabric8/maven/DeployToProfileMojo : Unsupported major.minor version 51.0
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>io.fabric8:fabric8-maven-plugin:1.2.0.redhat-046
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/Users/neto/.m2/repository/io/fabric8/fabric8-maven-plugin/1.2.0.redhat-046/fabric8-maven-plugin-1.2.0.redhat-046.jar
[ERROR] urls[1] = file:/Users/neto/.m2/repository/org/eclipse/aether/aether-api/0.9.0.M2/aether-api-0.9.0.M2.jar

And finally, I tried to execute the (and the, any container is created and I got the following message:
retrying (attempt 1) ...
retrying (attempt 2) ...
retrying (attempt 3) ...
64451 [pool-2-thread-1] WARN org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier - Server at / presented unverified key:
Waiting for container: root
Waiting for container root to provision.
Using specified zookeeper password:admin
To stop the backgroud Fuse process, please go to bin and execute stop

Finally, I followed step-by-step the demo guide. And I configured everything else (MVN_HOME; I put it in my OS Path, the .m2/settings.xml). Do you think that it is due to a configuration problem, or have you any idea for a solution to my problem?

Thanks for the attention,
Unknown said…
Hi Christina, I have a Cluster Master / Slave MQ installed in 3 nodes, the temp is that I try to scalar and always process the messages approximately 1000 requests per minute, whatever I do I always have the same processing time, which parameter I have to fine tune So that the processing is faster?

Popular posts from this blog

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…

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 。

JBoss Fuse - Fuse workshop 101 - Part One

On my way to Hong Kong for a day of workshop on JBoss Fuse, and as I go through my Slide deck, I cannot find any decent easy workshop for beginners. Therefore I decide make a workshop that is easy for Camel first timer to get their hands dirty.

The first of part of the workshop is an introduction to Camel, it first goes through what is exactly inside JBoss Fuse.

For part one of the workshop, it takes your through the very basic of Camel, one of the very important component inside JBoss Fuse.
Every Camel need to have a runtime container to run in, inside camel we call it a CAMEL CONTEXT.  Inside every Camel context, you can define lots of camel route and registry, don't worry about what those are, we will explain later.

So inside out blueprint xml, you will see a tag called camelContext.

Next up is camel route, they are a chain of command or process defined by you, as a developer.
Inside the camel route, there are consumer endpoints that listens to the incoming messages, producers …