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:
https://github.com/weimeilin79/failoverdemo

Before begin, there are some setups you need to do,
Download JBoss Fuse from http://www.jboss.org/products/fuse/overview/



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.

<server>
  <id>fabric8.upload.repo</id>
  <username>admin</username>
  <password>admin</password>
</server>

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

  • init.sh
    • 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
  • install-all.sh  
    • 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

Comments

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 org.apache.karaf.shell.console.jline.TerminalFactory.destroy(TerminalFactory.java:42)
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 init.sh (and the init_all.sh), 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 /0.0.0.0:8101 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,
Neto
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 JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.


2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.


So, now we know …

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 …

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 …