webMethods異常-UM當機處理

1.今天下午使用者發現資料一直不能發送成功，回報給EDI的同僚

2.登陸到IS上進行檢查Log中的Error

系統報錯：

The session is not currently connected to the server. Unable to perform the request:Session has been closed

懷疑Message的Session無法連接配接了，然後排查Message的面闆中的下面的資訊

webMethods Messaging Settings中的Universal Messaging挂掉了。

 webMethods Messaging Trigger Management中的Trigger Connection 全部不能連接配接了

3.登陸到UM的伺服器，路徑如下:/opt/softwareag/UniversalMessaging/server/umserver/data

檢視nirvana.log，具體原因是因為Server shutdown initiated due to OutOfMemoryException，伺服器因為應用記憶體溢出導緻shutdown了

[Fri Nov 23 13:38:00 CST 2018] [MemoryManagement] [com.pcbsys.foundation] - MemoryManager: Monitor: Memory Free, Before 185.81 MB, After 185.81 MB
[Fri Nov 23 13:38:34 CST 2018] [MemoryManagement] [com.pcbsys.foundation] - MemoryManager: Monitor: Memory Free, Before 184.87 MB, After 184.87 MB
[Fri Nov 23 13:38:42 CST 2018] [Scheduler Worker Pool:1] [com.pcbsys.nirvana.server] - Server shutdown initiated due to OutOfMemoryException in Scheduler Worker Pool:1
[Fri Nov 23 13:38:42 CST 2018] [Scheduler Worker Pool:1] [com.pcbsys.nirvana.server] - Autogenerated thread dump


"MemoryManagement" daemon prio=1 tid=0xb TIMED_WAITING
	at java.lang.Thread.sleep(Native Method)
	at com.pcbsys.foundation.memory.fMemoryManager.run(fMemoryManager.java:381)
	at com.pcbsys.foundation.threads.fThread.localRun(fThread.java:113)
	at com.pcbsys.foundation.threads.hThread.run(hThread.java:108)
	at java.lang.Thread.run(Thread.java:748)
           

4.既然UM記憶體不夠，增加UM記憶體，具體設定路徑:

cd /opt/softwareag/UniversalMessaging/server/umserver/bin
           

修改 Server_Common.conf這個檔案的關于UM記憶體的資訊，具體修改如下:

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=8192

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=8192
           

修改完成後。

5.準備重新啟動UM，在重新啟動UM前，請先儲存Trigger的消息。

 然後使用如下指令，檢查UM的運作線程

ps -ef|grep umserver
           

因為該UM當機,是以沒有運作線程，直接啟動即可。

啟動的指令如下:

#進入bin路徑
cd /opt/softwareag/UniversalMessaging/server/umserver/bin
#啟動UM
nohup ./nserver &
#檢視UM線程是否存在
ps -ef|grep umserver 
           

發現UM已經啟動了

7.檢視Log資訊,記憶體剩餘量6.5GB

MemoryManager: Monitor: Memory Free, Before 6.51 GB, After 6.51 GB

[Fri Nov 23 17:15:35 CST 2018] [MemoryManagement] [com.pcbsys.foundation] - MemoryManager: Monitor: Memory Free, Before 6.51 GB, After 6.51 GB
[Fri Nov 23 17:15:40 CST 2018] [UM Server Status Generator] [com.pcbsys.foundation] - ServerStatusLog> Memory=6667, Direct=1024, EventMemory=0, Disk=361911, CPU=0.5, Scheduled=201, Queued=0, Connections=62, BytesIn=81929, BytesOut=2558280, Published=13, Consumed=18
[Fri Nov 23 17:15:45 CST 2018] [UM Server Status Generator] [com.pcbsys.foundation] - ServerStatusLog> Memory=6667, Direct=1024, EventMemory=0, Disk=361911, CPU=0.25, Scheduled=201, Queued=0, Connections=62, BytesIn=84080, BytesOut=2571650, Published=14, Consumed=19
           

8.最後一步是啟動Trigger