Perform maintenance is failing

Which IIQ version are you inquiring about?

Version 8.4

Share all details related to your problem, including any error messages you may have received.

Hi Community,

Our performance maintenance task is failing in one of the lower environments. Please help us to resolve the issue.

Object pruning failed with : java.lang.OutOfMemoryError: Java heap space

It runs for more than 30 - 40 hours and fails.

Increase Java Heap memory

1 Like

done but still not helping the task stalls for a long time.

PM task is system maintenance task perform lot many operation , time taken is totally depend on the option you select and also configuration and data in your system .
Prune identity snapshots, task results, and certifications. Perform other background maintenance tasks.

1 Like

Try enabling partitions on the task if you are on 8.2 or above

1 Like

Go into the Request Objects page and see how many Requests theres is hanging , if is a lower environment you can delete these. remember , only if they are not important.

And Enable Partition.

Also what options do you have on the task?

Best!

2 Likes

Apart from heap it’s better to check log file to see exact issue as we recently faced lazy hibernate expection

1 Like

Hi and Hello,

It sounds like you’re encountering a Java heap space OutOfMemoryError during a long-running performance maintenance task. This error typically occurs when the Java Virtual Machine (JVM) runs out of memory in the heap space, which is where it allocates memory for object storage. Here are several steps and considerations to help you resolve this issue:

  1. Increase Heap Size: If your application’s heap size is not sufficiently large to handle the workload, you can increase it. This is done by adjusting the -Xmx parameter, which sets the maximum heap size. For example:

java -Xmx4g -jar yourApplication.jar

This command increases the maximum heap size to 4 GB. Adjust the size according to your server’s physical memory availability.

  1. Optimize Java Garbage Collection: Tuning the garbage collector can help manage memory more efficiently. For long-running tasks, consider using the Concurrent Mark Sweep (CMS) or G1 garbage collectors, which are better for responsive systems and large heap sizes. Configure the garbage collector with JVM options, such as:

java -XX:+UseG1GC -jar yourApplication.jar

  1. Analyze Memory Usage: To better understand memory consumption, you can analyze heap usage using tools like:
  • VisualVM
  • JConsole
  • HeapDump: Generate a heap dump at the point of failure using -XX:+HeapDumpOnOutOfMemoryError. You can analyze this dump with tools like Eclipse Memory Analyzer (MAT) to identify memory leaks or large objects.

Regards,
Adam

5 Likes

I think @AdamVentum has provided the recommended solution in detail

@charan18 : let us know if issue is still there :slight_smile:

Hi All,

Thanks for sharing lot of knowledge on the issue the issue now resolved.

We had lot of syslogs around 1.1bn of them which didn’t let PM task to be running.
We cleared the syslogs from DB table and now the PM is running fine.

Thansk

2 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.