Skip to main content

JEAP 5 - Shared Library設定

通常在JBoss 裡面,如果有遇到不同的Application 需要共用一些JAR的檔案,我們都會請他放在 JBOSS_INSTALL_PATH/server/$PROFILE/lib 下。

這種Loading 的方式,會將EAR 與 這些library 分別Load 近來。

因此,load 之後,兩個 EAR 都會對應到同一個 Load 進來的Library的instance.


使用者希望可以把這些jar檔放在一個位置,以後只要更新一個地方,其他對應的EAR 只要look up 這些更新得檔案就好了。

通常,一般的Class 這樣子就好了。因為大部份的API 在同一個Server instance 下是可以共用的。這樣也比較省memory。




可是這位客戶,它的Library裡面因為會需要hold 住每個EAR instance 給它的值,所以是無法提供共用的。

因此,他希望每個Library 都存在每個獨立EAR isolation 的裡面,不要互相影響。


照現行的deploy的做法是沒辦法做到 isolation 的。

唯一的方法就是在JBoss deploy 的時候去定義,讓他在load EAR 的時候也去look up 設定的library 位置。

所以,必須要客制化一個deployer 讓它可以在EAR Level 的時候lookup 檔案,做到這一層的isolation.

在網路上找到一個Sample Code, 它的做法是extend JBoss 原有的UrlIntegrationDeployer,這支程式會把程式掃到的URL File load 進去。 所以要改的工,變得簡單了。

1. 先建立一個JMX Bean, 指定需要額外讀取的檔案。
2. 找一個可以實作isIntegrationDeployment的method. (PathUrlIntegrationDeployer)

接下來只要將檔案放到JBOSS_INSTALL_PATH/server/$PROFILE/deployer 下,修改裡面loading 的位置就好囉!


因為這裡不能放檔案下載,所以有需要請跟我要吧!


另外,還有EAR isolation 的修改。
如果想要每個EAR 的 domain 獨立的話,JBOSS_INSTALL_PATH/server/$PROFILE/deployers/ear-deployer-jboss-beans.xml  裡面,isolated 改成 true


<bean name="EARClassLoaderDeployer" class="org.jboss.deployment.EarClassLoaderDeployer">
      <!-- A flag indicating if ear deployments should have their own scoped
         class loader to isolate their classes from other deployments.
      -->
      <property name="isolated">true</property>
   </bean>

Comments

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.) 這個參數是每一個應用程式都不一樣的。

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

Connection Pool 最多可以開啓的 connection 數量

prefill

事先將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 …