WebSphere 是 IBM 的軟件平臺。它包含了Web 應用程序和跨平臺、跨產品解決方案所需要的整個中間件基礎設施,如服務器、服務和工具等。在使用WebSphere的過程中,大家會遇到這樣那樣的問題,在此就常見錯誤做個解析與總結。
一、WAS應用無法正常停啓
有時會碰到正常停是停不了的應用,這是因爲系統裏進程的連接釋放不了。這時候直接在系統裏把應用的進程殺掉即可。
Scm01的停啓如下
首先登進10.8.2.201,執行以下命令
ps –ef|grep ScmWeb01
找到應用的進程,正常情況應該有兩個,網站空間,一個爲node的進程,一個爲server的進程,如下
先殺掉node的進程
kill -9 7427
注: //7427爲進程的pid號
接着殺掉server進程
kill -9 20287 //20287也是pid號
這時候應用就停了
啓動方法如下
先執行
/opt/IBM/WebSphere/ScmWeb01/bin/startNode.sh
然後執行
/opt/IBM/WebSphere/ScmWeb01/bin/startServer.sh Scm01
等到進程的pid號出現,香港服務器租用,server即啓起來了,這時候就可以通過訪問單個server的方式訪問了。
二、WAS 節點不同步解決辦法
節點不同步易產生的錯誤現象:
1、啓動應用的時候特別慢,報“可能已經啓動成功,但沒有在預定的時間啓動完成,詳情請參考日誌。
2、 “企業級應用程序”下應用的狀態好像不對,在WebSphere企業應用程序中啓動起來的應用在這裏仍然是“紅X”狀態。
3、系統管理下的節點狀態不對,同步節點後仍然顯示未同步。
4、部署新應用後啓動時,會報
[12-4-11 20:08:07:127 CST] 0000002b DefaultTokenP I HMGR0149E: 嘗試打開到核心組 DefaultCoreGroup 的連接被拒絕。發送進程的名稱爲
fqztestapCell01\fqztestapCellManager01\dmgr 且 IP 地址爲172.18.251.23。本地進程中的全局安全性爲 Disabled。發送進程中的全局安全性爲 Enabled。接收到的標記以????+?Qe?? 開頭。異常爲 <null>。
[12-4-11 20:20:40:736 CST] 00000017 AdminHelper A ADMN1009I: 嘗試啓動 rews_message_parse 應用程序。
[12-4-11 20:20:40:740 CST] 00000017 ApplicationMg W WSVR0215W: 啓動應用程序 rews_message_parse 失敗。尚未安裝該應用程序。
[12-4-11 20:42:21:326 CST] 00000016 AdminHelper A ADMN1009I: 嘗試啓動 rews_message_parse 應用程序。
[12-4-11 20:42:21:330 CST] 00000016 ApplicationMg W WSVR0215W: 啓動應用程序 rews_message_parse 失敗。尚未安裝該應用程序。
但實際部署的整個過程中,日誌沒有報錯且控制檯上提示部署成功。這種Was控制檯節點顯示同步狀態不正常,無法完成同步,問題解決如下:
1、切換到bin目錄下,執行相應命令,依次停止 server 、 node 、dmgr(嚴格按照此順序)
/opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin/stopServer.sh server1
/opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin/stopNode.sh
/opt/IBM/WebSphere/AppServer/bin/stopManager.sh
2、刪除 wstemp, temp 和 config/temp 文件夾下面的臨時文件
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/temp、wstemp、tranlog目錄下內容刪除。
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/temp目錄下內容刪除。
3、同步節點:
##同步節點信息
切換到“/opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin/”下:
執行 :syncNode.sh kmtest 8879 -username wasadmin -password 000000
其中 “kmtest”是was所部署在的主機名第二項即爲主機名
4、依次啓動 dmgr、node、server (嚴格按照此順序) #依次停止 server 、 node 、dmgr
/opt/IBM/WebSphere/AppServer/bin/startManager.sh
/opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin/startNode.sh
/opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin/startServer.sh server1
三、節點未激活
錯誤提示:Server cannot be started because the node agent for server server1 on node server1Node01 is not active.
在/opt/IBM/WebSphere/AppServer/bin下用startNode.sh起節點的時候報
ADMU0111E: Program exiting with error: java.io.FileNotFoundException:
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/server1Cell01/nodes/server1CellManager01/servers/nodeagent/server.xml
(No such file or directory)
這是因爲WAS管理控制檯上,節點啓停的真正的文件並不在這個目錄下
可以進到這個/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin目錄下
先啓節點
server1:/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin # ./startNode.sh
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 5894
再啓服務器
server1:/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin # ./startServer.sh server1
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 6121
然後向WAS管理控制檯加入該節點
server1:/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin # ./addNode.sh 192.168.0.8 8879 -username wasadmin -password 12345
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
CWPKI0308I: Adding signer alias "datapower" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
A9:BA:A4:B5:BC:26:2F:5D:2A:80:93:CA:BA:F4:31:05:F2:54:14:17
ADMU0001I: Begin federation of node server1Node01 with Deployment Manager at
192.168.0.8:8879.
ADMU0009I: Successfully connected to Deployment Manager Server:
192.168.0.8:8879
ADMU0033E: The node server1Node01 already has been added to the cell.
ADMU0027E: An error occurred during federation ADMU0033E: The node
server1Node01 already has been added to the cell.; rolling back to
original configuration.
ADMU0211I: Error details may be seen in the file:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.log
ADMU0111E: Program exiting with error:
com.ibm.ws.management.tools.DoNotDoAddNodeException: ADMU0033E: The
node server1Node01 already has been added to the cell.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.log
然後在控制檯裏看節點已正常並已運行了。