Search Engine: Elastic

Article ID: 131643, created on Oct 20, 2017, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 7.2


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

/var/log/pa/pui/pui.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/pa/console.log

171011 10:54:45 INFO  [stdout] (default task-114) Turbine: Double initializaton of Turbine was attempted!
java.lang.OutOfMemoryError: GC overhead limit exceeded
Dumping heap to /var/log/pa/java_pid2624.hprof ...
Heap dump file created [2910748866 bytes in 27.098 secs]


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


As an immediate resolution, restart the service:

# service pau restart

For permanent resolution, contact Odin Technical Support to provide root cause analysis.

If the issue is repeatable and amount of RAM on the UI node allows, the memory limit can be increased:

  • Edit the Wildfly configuration file:

    [root@ui ~]# grep Xmx /usr/local/pem/wildfly-10.1.0.Final/bin/standalone.conf
       JAVA_OPTS="-Xms64m -Xmx2048m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m"

    and change it to:

    [root@ui ~]# grep Xmx /usr/local/pem/wildfly-10.1.0.Final/bin/standalone.conf
        JAVA_OPTS="-Xms64m -Xmx4096m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m"
  • Restart the UI service:

    # service pau restart

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 31987597efff5a3a9ce779cc203bbe5e 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF