UX Crash - "java.lang.OutOfMemoryError: Java heap space"

[anz.fin.all.mailbox]

Hello All,

We experienced an issue with UX last night where it stopped responding and it required a restart of the Apliqo Application Server Windows service. Everything else was working fine (Arc, Pulse, Perspectives, TM1 Web). We’ve been trying to find out what went wrong and we found in the UX catalina log the following entry at around the time UX stopped responding:

SEVERE [https-jsse-nio-8880-exec-3] org.apache.coyote.AbstractProtocol$ConnectionHandler.process Failed to complete processing of a request
	java.lang.OutOfMemoryError: Java heap space

Is anyone able to explain this error to us and whether or not it would have resulted in UX becoming unresponsive?

Thanks,
David

[rmazziero]

Hi David,

The application may be consuming all the available Java memory that was set during installation. Probably increasing it would solve it, assuming you have enough RAM memory available on the Server where Apliqo UX is installed.

See the details below for steps on how to check and increase the Java memory for Apliqo, these days it is recommended to leave at least 4096 MB (when installing the default Max value is set to 1024mb)

UX's Title Element selection just keep spinning

Hi @Lance.Wang , The config of the Java Memory for Apliqo is on the Server side, this is the memory the Apliqo UX Tomcat service. you can see details about it on this CODE article about Canvas, it is still similar, although the Tomcat version is updated for UX. You can also see the steps on how to change it from this older post below… I believe the only change is that the newer versions of UX would be using newer versions of Tomcat. On my machine is “tomcat9w.exe” for Version 2023.02 FP1. …

Hope this helps!

Rodrigo

[anz.fin.all.mailbox]

Thanks for the reply @rmazziero. We did have it set to 4096 but I have increased it and we will monitor it’s usage.

Thanks,
David

[sreepathy]

The Java heap space error that you are facing actually indicates that your JVM is running out of memory to allocate for objects in the heap. Which means, the Java Virtual Machine (JVM) running is actually running out of memory allocated to the Java heap. Even though you have already increased the JVM options this type of issue may come up if the application is holding on to objects longer than necessary.. This is because, always, JVM by default does not utilize the full container memory unless instructed to do so.

When the application comes to this state, the JVM can no longer process new requests, resulting in application unresponsiveness. So in this condition the next action would be to restart the application to bring things back to normal.

Since Arc, Pulse, Perspectives, and TM1 Web were still working, it indicates that they are running in separate processes and were unaffected by the memory issue in the UX JVM. So basically, this error is the direct cause of UX becoming unresponsive.

In order to avoid this issue, you may need to review and adjust the JVM heap size configuration. Then to monitor it in even intervals you can check with your GC logs and use profiling tools like HeapHero that will help you monitor memory usage patterns for potential leaks or spikes, and analyze logs such as GC logs to better understand memory behavior under load. You can check out this blog How to Solve OutOfMemoryError: Java heap space to understand more about this Java Heap Space error.