Search Engine: Elastic

Article ID: 130962, created on Jun 9, 2017, last review on Jun 9, 2017

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5


OA UI is down or UI Java process constantly consumes 100% CPU.

/var/log/poa-ui.log contains the entries:

2016-11-29 16:26:53,886 0b49b3d5a2 8373) DEBUG  ERR                  java.lang.OutOfMemoryError: Java heap space
2016-11-29 16:26:53,894            8354) DEBUG  ERR                  java.lang.OutOfMemoryError: Java heap

The following errors are logged to /var/log/catalina.out

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Receive Worker for ClientChannel: (iiop) (43017 -> 8409)"
Caused by: java.lang.OutOfMemoryError: Java heap space


Various reasons may occupy the whole Java heap space of the UI service.


As an immediate resolution, restart the service:

# service pemui restart

In order to trace down the cause of such issues, add the following adjustments to /etc/init.d/pemui:

correct the line:

export JAVA_OPTS="-server -Xms1024m -Xmx1024m -XX:MaxPermSize=128m -XX:+UseParallelOldGC -Dplesk.root=/usr/local/pem -Dfile.encoding=UTF-8 -Dorg.apache.coyote.USE_CUSTOM_STATUS_MSG_IN_HEADER=true "

so that it turns to:

export JAVA_OPTS="-server -Xms2560m -Xmx2560m -XX:MaxPermSize=128m -XX:+UseParallelOldGC -Dplesk.root=/usr/local/pem -Dfile.encoding=UTF-8 -Dorg.apache.coyote.USE_CUSTOM_STATUS_MSG_IN_HEADER=true -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/ -verbose:gc -Xloggc:/tmp/gc.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:GCLogFileSize=1M -XX:NumberOfGCLogFiles=5"

Restart the UI service afterwards:

# service pemui restart

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF