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.
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.
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:
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.
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
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.
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.