Hi,
We have been having Out-Of-Memory issues in our Production Weblogic 10.3.2 Servers that we use. So we are trying to replicate the OOM issue in our Test Servers. In this quest, we took the JRA recording for one of the Test Servers. We have attached the screen shot of GC pattern seen in JRMC. We tried to attach JRA file but it seems it is not allowed to. We have a total heap size of 2 GB and Nursery size of 512 MB. The GC strategy used is Genparpar. Please let us know if we need to do any sort of tuning to have better GC activity than what we have today. Also I have attached the exceptions that we encountered in Production Server and the Thread-Dump taken from Production Server but the JRA recording that is attached is from Test Server. We tried to replicate the OOM issue that we see in Production Server in Test Server but we haven’t achieved just yet and the reason why I say like this is because we haven’t seen any OOM issues getting reported in our Test Server logs.
Our concerns are as follows:
- Are we running the right GC mode with the right configuration or settings? Please let us know your suggestions from JRA recording that I have shared.
- The Old Collection is happening when we almost hit the roof of 2 GB. The Heap usage gradually increases to the max value and that is when Old Collection is being called and Heap memory usage comes down to 150 MB. We will have to see if we can have the Old Collection happening before even we hit the max value or close to max value. I am aware of the fact that we have the option of configuring ‘
gctrigger’ but as I understand this option is when we have Mostly Concurrent GC strategy. Currently, we are having Genparpar Strategy.
Please let me know if I need to furnish any more information.
Thanks in advance.
Regards,
-Sawan.Patwari