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