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_WAITINGat 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

總結

以上是生活随笔為你收集整理的webMethods异常-UM宕机处理的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。