Wikis - Page

(OO) Support Tip: Internal JVM monitoring

0 Likes
  • wrapper.log – monitors JVM via Tanuki (java service wrapper)

STATUS | wrapper  | <date>| Launching a JVM...

INFO   | jvm 1    | <date>| INFO: Server startup in [126,435] milliseconds

STATUS | wrapper  | <date>| <-- Wrapper Stopped

INFO   | jvm 1    | <date>| java.lang.OutOfMemoryError: Java heap space

STATUS | wrapper  | <date>| The JVM has run out of memory.  Restarting JVM.

INFO   | jvm 1    | <date>| Dumping heap to java_pid2084.hprof ...

Dumps are created on OOM only if flag is enabled in (central)-wrapper.conf !

wrapper.java.additional.7=-XX:+HeapDumpOnOutOfMemoryError

STATUS | wrapper  | <date>| Pinging the JVM took 20 seconds to respond.

STATUS | wrapper  | <date>| JVM appears hung: Timed out waiting for signal from JVM.  Restarting JVM.

Parameters that handle the keepalive with the JVM:

wrapper.ping.timeout=120

wrapper.ping.interval=10

wrapper.jvm_exit.timeout=60

wrapper.shutdown.timeout=120

  • Wrapper logging is available for almost all types of nodes. ( Central, RAS, Designer, SSX, Insights, Robot, Recorder, Studio)

Labels:

Support Tips/Knowledge Docs
Comment List
Related
Recommended