Skip to main content

Red Hat JBoss Fuse - Connecting to A-MQ in EAP with Camel

JBoss EAP has a built-in Messaging solution, HornetQ. Sometimes we need A-MQ for more protocol support, reliable messaging and HA capability. By connecting through the resource adaptor in EAP, we will be able to connect EAP to A-MQ.

First install the A-MQ library into EAP.

You can find it in the A-MQ zip file, under /jboss-a-mq-6.2.x.redhat-xxx/extras/,
in there you can find a file, unzip it, there you can locate the library we need in apache-activemq-5.11.x.redhat-62xxxx/lib/optional. 

  • activemq-rar-5.11.x.redhat-62xxxx.rar

Make sure you start up both the JBoss A-MQ(with ID/PWD: admin/admin) and JBoss EAP, go to the JBoss Admin Console located at http://localhost:9990 and logon with the ID/PWD previously set by you when installing. There are several options here,
  1. Install the libraries through deployment
  2. Install as module

So I am going to do the easy way, which is deploy the libraries. This is not recommended in production (since anyone with admin right and remove, disable the library..).  In the admin console, go to Runtime/Manage Deployments, and click on "Add" button to add the rar file.

After successful deployment, enable the rar file.

And we are now ready to start setting the resource adaptor. Go to Configuration -> Under Connector, click on Resource Adapters, and it will display the configuration page. Click on Add to add our new Resource, which A-MQ.

A screen will then pop-up, enter
which is the name when you deploy the library on EAP. And select XATransaction.

Under Properties tab, enter the following settings,

  • UserName: admin
  • Password: admin
  • UseInboundSession: true
  • ServerUrl: tcp://localhost:61616?jms.rmIdFromConnectionId=true

We can now setup the ConnectionFactory for the broker, first click on view in In the Connection Definition configuration page, click on add, a popup will appear, enter following information.

  • Name: localhostConnectionFactory
  • JNDI Name: java:jboss/jms/activemq/ConnectionFactory
  • Connection Class: org.apache.activemq.ra.ActiveMQManagedConnectionFactory

Under Properties, please enter the following config. 
  • UserName: admin
  • Password: admin
  • UseInboundSession: true
  • ServerUrl: tcp://localhost:61616?jms.rmIdFromConnectionId=true
And lastly, enable the connection factory.

This is what it looks like.

Normally, that is all we need for Camel application. BUT! If you would like to map to your messaging queue or topics via Message Driven Bean, we need to go for an extra step to create the adapter for Queue and Topics as well. Here I am going to use queue as an example.

Go to Admin Objects unser Resource Adapter,

Click on Add to add an admin object, enter:

  • Name:testQueue
  • JNDI Name:java:jboss/jms/amq/queue/testQueue
  • Class Name: org.apache.activemq.command.ActiveMQQueue

In Properties tab add

  • PhysicalName:TEST.QUEUE

And enable the testQueue.
And to add resource mapping to Message driven bean, we need to map the resource adapter to our message driven bean in the container, go to standalone.xml or domain.xml (depends on if you are in standalone or domain mode). Here I am starting using standalone mode, so I will open my standalone.xml under standalone/configuration folder in JBoss EAP. 

Under ejb3 subsystem, add mdb mapping. 

<subsystem xmlns="urn:jboss:domain:ejb3:1.5">
      <resource-adapter-ref resource-adapter-name="activemq-rar-5.11.0.redhat-620133.rar"/>
      <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>

That's it for the setting. You have successfully created a Resource Adaptor from JBoss EAP to JBoss A-MQ. 

To do a little testing, I created a small MDB project, 
we can map the destination queue to "queue/testQueue" 

package com.redhat.mdb;

import java.util.logging.Logger;

import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;

@MessageDriven(name = "TestMDB", activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/testQueue"),
@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge") })
public class TestMDB implements MessageListener {

  private final static Logger LOGGER = Logger.getLogger(TestMDB.class.toString());
  public void onMessage(Message recmsg) {
    TextMessage msg = null;
    try {
      if (recmsg instanceof TextMessage) {
        msg = (TextMessage) recmsg;"Received Message from queue: " + msg.getText());
      } else {
        LOGGER.warning("Message of wrong type: " recmsg.getClass().getName());
    } catch (JMSException e) {
      throw new RuntimeException(e);


Click here to download for the source code, if you would like to run it, please run
  • mvn clean install 

under the mdb project directory.

And then deploy the WAR file onto EAP. 

It will start printing our messages if we send message in to the queue, so, go to A-MQ admin console at http://localhost:8181, login with admin/admin, click on  ActiveMQ -> amq -> queue -> queue/testQueue, and then on the righthand side, click on the Send Tab. 
Here you can send data and messages into queue. 

And the result will appear in the log.

That's it. :)


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 。

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 …

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 …