I am using WLS 10.3.2 and IBM AIX 6 as the OS and IBM jdk.
The application running on the server hanged after the gc did not happen even after the free heap space falls to 0%. This condition where the gc did not happen even if the free heap space dropped to 0% remained for another 40 min. I had to restart the box to start the application again.
I was manually able to trigger gc through the console's Garbage Collect button. As soon as I pressed the Garbage Collect button, the free heap % shoots up to 90.The jvm garbage collected and freed the heap space.
This did happen but is there any way that through the WLS server I can make the GC to happen after the free heap space falls below a certain limit?
After a little research I found an option for the setDomainEnv.sh:
-XX:MinHeapFreeRatio & -XX:MaxHeapFreeRatio. Can this tag help the WLS to trigger GC to happen at a particular free heap space ratio?
-XX:MaxHeapFreeRatio= -- Maximum percentage of heap free after GC to avoid shrinking.
-XX:MinHeapFreeRatio= -- Minimum percentage of heap free after GC to avoid expansion.
Joseph Antoine Raja wrote:-XX:MaxHeapFreeRatio= -- Maximum percentage of heap free after GC to avoid shrinking.
-XX:MinHeapFreeRatio= -- Minimum percentage of heap free after GC to avoid expansion.