Skip to main content

JBoss Messaging - Client 無法連結Queue Server

今天有個客戶遇到這個問題,就順便PO 上來,
Exception 的內容如下

Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id xxx-xxxxx-1-xxxx-xxxx-xxxx
    at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:101)
    at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke
       (JMSServerInvocationHandler.java:157)
    at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:930)
    at org.jboss.remoting.transport.socket.ServerThread.completeInvocation
       (ServerThread.java:791)
    at org.jboss.remoting.transport.socket.ServerThread.processInvocation
       (ServerThread.java:744)
    at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:586)
    at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)
    at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:216)
    at org.jboss.remoting.Client.invoke(Client.java:2034)
    at org.jboss.remoting.Client.invoke(Client.java:877)
    at org.jboss.remoting.Client.invoke(Client.java:865)
    at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)

這個問題不好抓,原因是因為他並不是天天發生。通常是流量比較大的時候,突然就會跳出這個Exception, 讓人不勝其擾。而且只要restart sender 或是 receiver 就好了!

其實發生這個的原因不是 Message Server , 不要再怪它了,他只是因為很忙所以回應慢了點。無辜阿~ 

真正的原因是因為JBoss Container 內建的 JMS handler 他會定期去Check與Messaging Server 的連線,若是messaging server 回應時間太慢超過的設定的時間(validatorPingTimeout) 那就會把現在與queue 的連線關閉,可是Client 可能還在使用那個連線,這時如過還去使用那個關閉的連線,就會出現這個Exception了!

以下為圖示:














那該怎麼辦呢?
先講一下治標的辦法,因為timeout 的時候會把connection 關掉,那我們就把timeout 的時間延長到server 可以回應就好了。

延長Connection Timeout 的方式 

到 $JB_SERVER/deploy/messaging/remoting-bisocket-service.xml 下修改 validatorPingTimeout 的時間(例如說加個10 秒的), 另外也要注意一下同時上面的兩個值也考慮加長,例如clientLeasePeriod 與 validatorPingPeriod 也要一起加長,server 都已經很忙了,就不要有事沒事去問它,你還活著嗎? 最好是以同上的%數增加,例如 validatorPingTimeout 是 15 秒的話,那clientLeasePeriodvalidatorPingPeriod分別就是30秒會比較好!


當然最好還治本的方式,想想,到底做了什麼讓Messaging Server 忙到沒有時間回應?可以減少發送的量?可以另外建立Cluster 分流?我的JBoss Messaging Server 是不是用資料庫當底層(建議),還是只是靠著基本的File IO (Default 的安裝方式)。




Comments

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 …

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

jboss-devstudio-9.0.0.GA-installer-eap.jar
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 …