Skip to main content

JBoss Fuse on xPaaS - IoT Mash-up Demo

There are 3 common protocols when it comes to messaging on Internet of Things,

MQTT - is OASIS standard, adopted by various vendor and companies, it is an extremely light weight transport, and is excellent for low computing power device, and platforms. And it only supports publish and subscribe mechanism. 

STOMP - is simple and lightweight (not as light as MQTT), it supports transport over websockets, and it is basically sending text through wires, very much like telnet.

AMQP - is a vendor neutral protocol over the wire, it supports rich sets of communication patterns, and it is accessible through a wide variety of APIs, such as JMS, JCA, WCF, Qpid, etc

All these are very easy to implement using Apache Camel. So I came up with a demo, showcasing these 3 common protocols. 

The basic architecture of demo is basically like this: 

Where I have created different connectors, like MQTT, AMQP, STOMP, WebSocket and Openwire for a broker on top of OpenShift, or it's similar if you want to create this on a Local JBoss Fuse. 
To do that, go to the boker.xml setting (depending on your environment, if you create a new broker profile on Fuse, make sure you make a copy of broker.xml from mq.base profile to your broker profile.), add transportConnector with different protocol name and port. 

<transportConnector name="amqp" publishedAddressPolicy="#addressPolicy" uri="amqp://${OPENSHIFT_FUSE_IP}:5672"/>       

<transportConnector name="mqtt" publishedAddressPolicy="#addressPolicy" uri="mqtt://${OPENSHIFT_FUSE_IP}:1883"/>      

<transportConnector name="stomp" publishedAddressPolicy="#addressPolicy" uri="stomp://${OPENSHIFT_FUSE_IP}:31613"/>      

<transportConnector name="websocket" publishedAddressPolicy="#addressPolicy" uri="ws://${OPENSHIFT_FUSE_IP}:31614"/>

Then install 3 Camel Routes, all of them are using built-in Components in JBoss Fuse to poll in the message from broker. With the built-in component, it will save lots of code implementation time.

AMQP Component: 

MQTT Component: 

STOMP Component: 


As you can see from the camel route, after we retrieve messages, we will process it and put them all into a big queue, which will be picked up later by web application and displayed. 

Because we are using openshift as our broker, we need to export the internal port by using the port-forward command provided by the openshift client tool.

rhc port-forward containerName

And lastly, we are going to startup a local web application, so we can have a nice web interface let you play with different protocol and display the result in a web console. And within the web application, we also use Qpid API and MQTT API to send messages into the queue or topics. 

You can find the demo code here:

Here is the video demo: 


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 …

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 …