search cancel

AUTOMIC WORKLOAD AUTOMATION Analytics backend : Java crash

book

Article ID: 189338

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

I install analytics 12,3,2 on a separate server to collect data from AE 12.3.2

When I launch the backend, after a couple of minutes, I have a java dump that is generated.

 

Cause

We can see that the outofmemory error in the analytics_backend log

2020-04-15 10:55:04.894 ERROR 120206 --- [CollectorThread-3] o.s.s.s.TaskUtils$LoggingErrorHandler    : Unexpected error occurred in scheduled task.


net.jodah.failsafe.FailsafeException: java.lang.OutOfMemoryError: GC overhead limit exceeded

        at net.jodah.failsafe.SyncFailsafe.call(SyncFailsafe.java:159)

        at net.jodah.failsafe.SyncFailsafe.run(SyncFailsafe.java:81)

        at com.automic.analytics.backend.data.common.collector.ScheduledCollector.run(ScheduledCollector.java:132)

        at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)

Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded

Environment

AUTOMIC WORKLOAD AUTOMATION

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

Command used to launch Analytics backend in the service manager can be found by right click on Analytics backend service manager dialog and click on properties

 "C:\Program Files\Java\jre1.8.0_241\bin\java -Xmx3096M -jar analytics-backend.jar"

We need to verify if there is enough physical memory on the server. In this case, it was 15 GB

We increased the  maximum memory allocation pool for a Java virtual machine to 4096 as follows in the command used to launch Analytics backend in the service manager

"C:\Program Files\Java\jre1.8.0_241\bin\java -Xmx4096M -jar analytics-backend.jar" 

After restart the Analytics backend the problem was solved