Skip to main content

JEAP 5 - 幫J老闆減肥,減少不必要模組負擔

今天有客戶抱怨為什麼啟動J老闆要花5分鐘的時間?好久噢!
雖然我覺得跟我以前常用大藍的"網路球" 比起來已經是天上跟地下了~~
但是,5分鐘是真的有點誇張!!

J老闆非常有彈性 XD,上面所有的東西都像樂高一樣可以拆來拆去!
它的All Profile 裡面,為了要提供許多功能,所以是所有profile裡面的最肥的
據我多年(不要亂猜~我沒有很老) 的經驗,大部份AP根本不會用到它50%的功能!
所以很多功能都只是放在那裡白白的消耗資源!
(JBoss 再startup 的時候,就會把deploy的東西都load 進memory!
可是這些功能並不一定會用到)

那~要減肥也不能把自己的肝砍掉吧 !?
下面就是各功能對應的檔案,list 出來給大家,不要真把自己的有在用的肝砍掉阿XD


如果沒有用 JMS 功能 (provided via JBoss Messaging), 可以移除
  •  $CONFIG/deploy/messaging/
  • $CONFIG/deploy/jms-ra.rar
  • $CONFIG/deployers/messaging-definitions-jboss-beans.xml
  •  $CONFIG/conf/jbossts-properties.xml 裡面的 "XAResourceRecovery.JBMESSAGING1" mark :

<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1" value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/DefaultJMSProvider"/>


如果沒有用 Mail 的功能的話,可以把這兩個檔案移掉
  • $CONFIG/deploy/mail-service.xml
  • $CONFIG/deploy/mail-ra.rar

如果不用 BeanShell scripts, 把這個移除
  • $CONFIG/deployers/bsh.deployer

如果沒有用EJB 3的話,請移除
  • $CONFIG/deploy/ejb3-connectors-jboss-beans.xml
  • $CONFIG/deploy/ejb3-container-jboss-beans.xml
  • $CONFIG/deploy/ejb3-interceptors-aop.xml
  • $CONFIG/deploy/ejb3-timerservice-jboss-beans.xml
  • $CONFIG/deployers/ejb3-deployers-jboss-beans.xml
  • $CONFIG/deployers/jboss-ejb3-endpoint-deployer.jar
  • $CONFIG/deployers/jboss-ejb3-metrics-deployer.jar
  • $CONFIG/deployers/ejb3.deployer/
  • 然後在deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml 裡面的WarDeployer bean 裡面加上



<property name="persistenceUnitDependencyResolver"><null/></property>




如果沒有用EJB 2 的話 (老天保佑最好沒有~不然本身AP就慢了,神都救不了了!)移除

  • $CONFIG/deploy/ejb2-container-jboss-beans.xml


 
  • $CONFIG/deploy/ejb2-timer-service.xml
 (移除這個EJB 3可能會掛掉)
如果APweb services 沒有使用UDDI的話, 可以移除

  • $CONFIG/deploy/juddi-service.sar
如果AP裡面沒有timer 的定時作業,也沒用到 EJBtimer 的話,可以移除

  • $CONFIG/deploy/schedule-manager-service.xml
  • $CONFIG/deploy/scheduler-service.xml
  • $CONFIG/deploy/quartz-ra.rar
  • $CONFIG/deploy/ejb3-timerservice-jboss-beans.xml
  •  $CONFIG/deploy/ejb2-timer-service.xml
如果不需要 web services, 請殺掉

  • $CONFIG/deploy/jbossws.sar
  • $CONFIG/deployers/jbossws.deployer
今天沒有圖~看起來好無聊噢!放個照片讓我的小可愛Puji亮亮相好了 !




對了!感謝某位大哥詢問,
如果發生很多dependency 的的warning log,其實沒有關係,
但是如果覺得很煩,可以關掉 (EJB 部分,其他我還沒空try)


jboss-as/server/node4/deployers/jbossws.deployer/META-INF/jbossws-deployer-jboss-beans.xml
1.  關掉WebServiceDeployerEJB 的dependency 
  <bean name="WebServiceDeployerEJB" class="org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB">
   <!-- <depends>EJB2xDeployer</depends>
    <depends>Ejb3Deployer</depends>-->
  </bean>
2. 拿掉ejbReferenceResolver 關係
  <bean name="WSInjectionMetaDataDeploymentAspect" class="org.jboss.wsf.container.jboss50.deployment.metadata.InjectionMetaDataDeploymentAspect">
    <property name="requires">WebMetaData</property>
    <property name="provides">InjectionMetaData</property>
    <property name="ejbReferenceResolver"><null/></property>
  </bean>



Comments

Popular posts from this blog

Red Hat Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

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 。
加上…

Fuse - Contract First API Design with Apicurio and Fuse/Camel - Part One

This is part one of my two-article series that demonstrates the approach of implementing contract-first API design using Apicurioand Red Hat Fuse.

It covers how to create an OpenAPI standard document as the contract between API providers and consumers using Apicurio. It also shows how to quickly create mock tests using Red Hat Fuse.

There are two common approaches of creating these APIs.
Code FirstContract First Coming from a old time ESB developer, these are not new. We have been doing this forever. Before, it was the WSDL that define the contract of the service. we were doing a lot more code first, for me it's simply because it's much easier for me to write couple of Java classes and generate the WSDL for my consumer. 

It's often pretty straightforward if the consumer of your application has finalized how they want the service to be like. But you and I all know this is not often the case. So I had to go back to my code, and make the changes accordingly and pray I did not …