Hi community,
i have a really big problem, i sould deploy some developpement but they don’t want saying that our products aren’t stable, and i need strongly your help,
The problem is that after every weekend we found our UMs down, when we check our log we found those message :
2016/10/10 11:03:47 | Shutting down Nirvana Realm
INFO | jvm 1 | 2016/10/10 11:03:48 | Realm shutdown complete
INFO | jvm 1 | 2016/10/10 11:03:48 | Nirvana Realm has been shutdown
STATUS | jvm 1 | 2016/10/10 11:03:48 | Stopping Wrapper monitor on port:9998
INFO | jvm 1 | 2016/10/10 11:03:48 | [Mon Oct 10 11:03:48 GMT 2016],Server shutdown initiated due to JVM Exit Handler called
INFO | jvm 1 | 2016/10/10 11:03:49 | [Mon Oct 10 11:03:48 GMT 2016],Shutdown: Status updates shutting down
STATUS | jvm 1 | 2016/10/10 11:03:49 | Nirvana Realm already shutdown
STATUS | wrapper | 2016/10/10 11:03:50 | ← Wrapper Stopped
STATUS | wrapper | 2016/10/10 11:39:51 | Pinging the JVM took 78633 seconds to respond.
STATUS | wrapper | 2016/10/10 13:27:27 | TERM trapped, but ignored.
STATUS | wrapper | 2016/10/10 13:34:06 | → Wrapper Sta
2016/10/15 00:46:45 | Pinging the JVM took 21 seconds
2016/10/15 03:03:54 | Nirvana Realm Server shutting down due to OutOfMemoryException in Scheduler Worker Pool:4
INFO | jvm 1 | 2016/10/15 03:05:07 | Nirvana Realm Server shutting down due to OutOfMemoryException in Scheduler
the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 06:16:41 | Pinging the JVM took 3 seconds to respond.
STATUS | wrapper | 2016/10/19 06:17:42 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 06:18:42 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 06:21:52 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 06:25:00 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 06:29:12 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 06:31:15 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 06:33:22 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 06:34:56 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 06:38:05 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 06:41:43 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 06:42:45 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 06:45:54 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 06:49:03 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 06:50:03 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 06:54:15 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 06:55:16 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:01:35 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 07:04:43 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:08:54 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:11:01 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:16:13 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:20:27 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:22:34 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:23:37 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:24:38 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:26:46 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 07:29:54 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:30:56 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:31:58 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:34:05 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:37:15 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 07:39:21 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:42:31 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 07:45:39 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:47:43 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:48:44 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:49:46 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:52:55 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:58:07 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 07:59:09 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 08:01:17 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 08:01:49 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 08:03:23 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 08:04:25 | Pinging the JVM took 2 seconds to respond.
STATUS | wrapper | 2016/10/19 08:07:34 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 08:10:39 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 08:13:48 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 08:18:26 | Pinging the JVM took 1 seconds to respond.
STATUS | wrapper | 2016/10/19 08:26:17 | Pinging the JVM took 3 seconds to respond.
STATUS | wrapper | 2016/10/19 08:27:17 | Pinging the JVM took 2 seconds to respond.
it still ping until it shutdown on the weekend,
we are on webMethods 9,7 AIX, IS_9.7_Core_Fix9,
i found on the internet this [b]https://wrapper.tanukisoftware.com/doc/english/prop-ping-alert-x.html[/b] but i didn’t understand what’s the relation between wrraper monitoring and UM,
any suggestions please,
Regards,
Nezha