Skip to main content

JEAP 6 - J老闆需要綁定的Socket 設定

新的J 老闆用到的port 比之前更少了,而且現在全部寫在一個File裡面。感覺上又更好設定拉!

以下的清單是JEAP 6 使用的port. 供大家參考囉!
Name
Port
Mulicast Port
Function Description
Default Server Port
full-ha-sockets
full-sockets
ha-socket
standard-socket
Mmgt Web Console
9990

內建的管理的Console
No
Yes
Yes
Yes
Yes
Native
Mmgt
9999

管理Console,管理的API 或是 CLI 呼叫的port
No
Yes
Yes
Yes
Yes
ajp
8009
Apache JServ Protocol.
如果使用 HTTP Cluster load Balance 會用到
No
Yes
Yes
Yes
Yes
http
8080
開發網頁應用程式預設的Port
Yes
Yes
Yes
Yes
Yes
https
8443
加密後的SSL 連結 Port
No
Yes
Yes
Yes
Yes
jacorb
3528
JTS 交易的CORBA 服務 與其他 ORB-相關的服務使用.
Yes
Yes
Yes
No
No
jacorb-ssl
3529
CORBA SSL-加密的服務
No
Yes
Yes
No
No
jgroups-diagnostics
7500
找尋HA Cluster 中每個點(peer) port
No
Yes
No
Yes
No
jgroups-mping
45700
首次找尋HA Cluster 的成員使用的port
No
Yes
No
Yes
No
jgroups-tcp
7600
找尋HA Cluster 中每個點(peer) port TCP
No
Yes
No
Yes
No
jgroups-tcp-fd
57600
用來偵測HA環境中錯誤的port TCP
No
Yes
No
Yes
No
jgroups-udp
55200
45688
找尋HA Cluster 中每個點(peer) port UDP
No
Yes
No
Yes
No
jgroups-udp-fd
54200
用來偵測HA環境中錯誤的port UDP
No
Yes
No
Yes
No
messaging
5445
JMS service.
No
Yes
Yes
No
No
messaging-group
HornetQ JMS 用來廣播與找尋同一群組使用
No
Yes
Yes
No
No
messaging-throughput
5455
JMS Remoting.
No
Yes
Yes
No
No
mod_cluster
23364
Mod_cluster 使用的port,負責與Load balancer 之間的廣播
No
Yes
No
Yes
No
osgi-http
8090
內建OSGI 元件必須使用的port
Yes
Yes
Yes
Yes
Yes
 remoting
4447
EJB/JNDI Remote 的時候必須用到的Port
Yes
Yes
Yes
Yes
Yes
txn-recovery-environment
4712
JTA transaction recovery manager.
Yes
Yes
Yes
Yes
Yes
txn-status-manager
4713
JTA / JTS transation manager.
No
Yes
No
No
No

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 …