Skip to main content


(純粹是因為個人習慣用Linux 跟 Mac 的指令,對於古早的UNIX不習慣的呻吟 哈!)

要用JBoss Cluster 做Load Balance, 一般來說在JEAP 5 都是用mod_jk
因為實在是太多太多太多網路上的文件了,所以我就不寫了 (而且因為本人已經做到爛了~再寫我就要吐了)

紅帽不支援在AIX上的Web Server, 所以只好延用AIX 上面的IBM Http Server (IHS)

我本來也想要用mod_jk,就像之前我在centOS上面重新compiler 那個.so 檔案一樣。。
可是查了一下網路,看到那些gmake, gcc ....我就昏了!這...AIX 未免也複雜了吧!
(我不是C的專家。。我不是C的專家。。我不是C的專家。。我不是C的專家。。 )

後來發現IHS自己裡面已經內建了mod_proxy... 好吧!就是它了!

建置的方式 -> 使用AJP連結 (REVERSE)
Step 1.  到 IHS_HOME/conf/httpd.conf 把相關的Module 打開

LoadModule proxy_module modules/

LoadModule proxy_balancer_module modules/
LoadModule proxy_balancer_module modules/WebSphereCE/

LoadModule proxy_ajp_module modules/
LoadModule proxy_ajp_module modules/WebSphereCE/

Step 2. 在 IHS_HOME/conf/httpd.conf 裡面加上

<IfModule mod_proxy.c>
   <Proxy balancer://jbossCluster >
      Order deny,allow
      Allow from all

      BalancerMember ajp://server1:port1/somecxtPath route=node1 loadfactor=50

      BalancerMember ajp://server2:port2/somecxtPath route=node2 loadfactor=50
   <Location /balancer-manager>
      SetHandler balancer-manager
   ProxyPass /somecxtPath balancer://jbossCluster stickysession=JSESSIONID|jsessionid

Step 3. JBoss 上設定對應的node, 到 /JBOSS_HOME/server/INSTALL_PROFILE/deploy/jbossweb.sar/server.xml 裡面找到
Engine 開頭的 xml element, 加上 jvmRoute (記得每個node 都要取不同的名字)

<Engine name="jboss.web" defaultHost="localhost" jvmRoute="node1">

Step 4. 打開JBoss 的 Proxy設定, 到
/JBOSS_HOME/server/INSTALL_PROFILE/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml 裡面找到 關鍵字 useJK 改成true.

<property name="useJK">true</property>

注: mod_proxy 還有很多可以調整的部分,
例如 connectiontimeout等等...



Popular posts from this blog

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

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 …

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 …