2012-04-04 60 views
1

正如在標題中所述。之後,包裝器無法啓動另一個JVM,並且我的騾子服務停止。和線索呢?包裝ping超時和被困騾子

服務器有點負載,但負載不應該太大。

下面是相關的日誌:

發送一個數據包PING:OK
讀取數據包PING:從JVM
確定
得到ping響應發送一個數據包PING:平
發送一個數據包PING:平
發送一個數據包PING:平
發送一個數據包PING:平
發送一個數據包PING:平
發送一個數據包PING: ping
發送數據包PING:ping
JVM掛起:超時等待來自JVM的信號。
JVM沒有按要求退出,終止服務器偵聽端口32002.
在啓動另一個JVM之前等待5秒鐘。
信號被困。詳細信息:
信號編號= 17(SIGCHLD),來源=「未知」
收到SIGCHLD,檢查JVM進程狀態。
JVM響應信號SIGKILL(9)而退出。
JVM進程退出爲1的代碼,但是包裝退出代碼已經1
無法啓動JVM
< - 包裝停止

這裏是當我重新啓動騾子期運用日誌:騾子開始。

Working directory set to: /root 
Spawning intermediate process... 
Spawning daemon process... 
--> Wrapper Started as Daemon 
Using tick timer. 
server listening on port 32000. 
Classpath element, wrapper.java.classpath.1, does not exist: %MULE_LIB% 
Command[0] : java 
Command[1] : -Dmule.home=/opt/skybus 
Command[2] : -Dmule.base=/opt/skybus 
Command[3] : -Djava.net.preferIPv4Stack=TRUE 
Command[4] : -XX:MaxPermSize=128m 
Command[5] : -Djava.endorsed.dirs=/opt/skybus/lib/endorsed 
Command[6] : -Xms2048m 
Command[7] : -Xmx2048m 
Command[8] : -Djava.library.path=%LD_LIBRARY_PATH%:/opt/skybus/lib/boot 
Command[9] : -classpath 
Command[10] : %MULE_LIB%:/opt/skybus/conf:/opt/skybus/lib/boot/mule-module-boot-  3.2.1.jar:/opt/skybus/lib/boot/log4j-1.2.14.jar:/opt/skybus/lib/boot/mule-module-reboot-3.2.1.jar:/opt/skybus/lib/boot/wrapper-3.2.3.jar:/opt/skybus/lib/boot/commons-cli-1.2.jar:/opt/skybus/lib/boot/mule-module-logging-3.2.1.jar 
Command[11] : -Dwrapper.key=XmncggXh3D4jnC8q 
Command[12] : -Dwrapper.port=32000 
Command[13] : -Dwrapper.jvm.port.min=31000 
Command[14] : -Dwrapper.jvm.port.max=31999 
Command[15] : -Dwrapper.debug=TRUE 
Command[16] : -Dwrapper.pid=30321 
Command[17] : -Dwrapper.version=3.2.3 
Command[18] : -Dwrapper.native_library=wrapper 
Command[19] : -Dwrapper.service=TRUE 
Command[20] : -Dwrapper.cpu.timeout=10 
Command[21] : -Dwrapper.jvmid=1 
Command[22] : org.mule.module.reboot.MuleContainerBootstrap 
Command[23] : start0 
Launching a JVM... 
Starting the Mule Container... 
WrapperManager class initialized by thread: main Using classloader: [email protected] 
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org 
    Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. 

Wrapper Manager: JVM #1 
Running a 32-bit JVM. 
Wrapper Manager: Registering shutdown hook 
Wrapper Manager: Using wrapper 
Load native library. One or more attempts may fail if platform specific libraries do not exist. 
Loaded native library: libwrapper-linux-x86-32.so 
Calling native initialization method. 
Inside native WrapperManager initialization method 
Java Version : 1.6.0_10-beta-b25 Java HotSpot(TM) Server VM 
Java VM Vendor : Sun Microsystems Inc. 

WrapperManager.start([email protected], args["start0"]) called by thread: main 
Control event monitor thread started. 
Startup runner thread started. 
Communications runner thread started. 
Open socket to wrapper...Wrapper-Connection 
Opened Socket from 31000 to 32000 
Send a packet KEY : XmncggXh3D4jnC8q 
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) 
accepted a socket from 127.0.0.1 on port 31000 
read a packet KEY : XmncggXh3D4jnC8q 
Got key from JVM: XmncggXh3D4jnC8q 
send a packet LOW_LOG_LEVEL : 1 
send a packet PING_TIMEOUT : 30 
send a packet PROPERTIES : (Property Values) 
Start Application. 
send a packet START : start 
Received a packet LOW_LOG_LEVEL : 1 
Wrapper Manager: LowLogLevel from Wrapper is 1 
Received a packet PING_TIMEOUT : 30 
PingTimeout from Wrapper is 30000 
Received a packet PROPERTIES : (Property Values) 
Received a packet START : start 
calling WrapperListener.start() 
Waiting for WrapperListener.start runner thread to complete. 
WrapperListener.start runner thread started. 
2012-04-01 14:53:42,297 INFO [org.mule.module.launcher.MuleContainer] - < 
********************************************************************** 
* Mule ESB and Integration Platform         * 
* Version: 3.2.1 Build: 23380          * 
* MuleSoft, Inc.              * 
* For more information go to http://www.mulesoft.org     * 
*                 * 
* Server started: 12-4-1 下午2:53         * 
* JDK: 1.6.0_10-beta (mixed mode)         * 
* OS: Linux (2.6.18-92.el5xen, i386)         * 
* Host: localhost.localdomain (10.123.75.149)      * 
**********************************************************************> 
+0

下面是我重新開始使用騾子的日誌:mule start – 2012-04-04 01:11:16

回答

1

從第一個日誌文件,我可以看到JVM反應遲鈍到包裝的ping請求:

send a packet PING : ping 
send a packet PING : ping 
send a packet PING : ping 
send a packet PING : ping 
send a packet PING : ping 
send a packet PING : ping 
send a packet PING : ping 

所以包裝假定JVM被凍結,因此試圖停止並重新啓動它。但事實上,由於負載過重,Wrapper甚至無法啓動另一個JVM實例。 您可以擴展wrapper.ping.timeout,如果您的計算機上頻繁發生重負載,這將爲JVM提供更多時間處理ping請求。

http://wrapper.tanukisoftware.com/doc/english/prop-ping-timeout.html

希望這有助於你出去。

乾杯