Hi Manni,
In your GCeasy report, I could see that continuous Full GC events have occurred. As per my knowledge, this might be a reason your application is not responding and continuous Full GC events might also cause an OOM.
How to know memory accumulation leading to OutOfMemory error is a Tomcat problem or a problem of the Java application that runs in Tomcat?
Dear all,
on this GC log it covers a Tomcat OOM situation on Jan 26 ~07:30, but it somehow recovered from that. Only the next morning it was hanging and responding with "500" code (but no OOM in the log for this morning). But I saw this before, after a OOM situation, if it somehow recovers, it is still necessary to restart Tomcat.
One question that I have is: how can I know if this memory accumulation leading to OOM is a Tomcat problem or a problem of the Java application that runs in Tomcat.
Thank you in advance.
Best regards,
Manni
Report URL - https://gceasy.io/my-gc-report.jsp?p=c2hhcmVkLzIwMjEvMDEvMjcvLS1nYy5sb2cuMjAyMTAxMjUtLTEwLTUyLTI5&channel=WEB
View(s)
30- 0Like(s)
- 0Dislike(s)
- 0Saved
0
Share(s)
Facebook
Twitter
Email
Copy Link
sainath
Hi Manni,
1. By observing the above graph, every day in the morning around 8 AM - 9 AM suffering from consecutive full GCs. I suspect this is your peak volume time period. Maybe your traffic is growing higher. You might want to allocate more capacity. It can be done in two ways:
a. Increase JVM Heap Size:
Since you have allocated the JVM heap size around 3GB, then try increasing it to 4 GB and see whether it resolves the problem.
b. Add more JVM instances:
Adding more JVM instances is another solution to this problem. When you add more JVM instances, then traffic volume will get distributed. The amount of traffic volume handled by one single JVM instance will go down. If less traffic volume is sent to a JVM instance, then fewer objects will be created. If fewer objects are created, then you will not run into the consecutive Full GC problems.
2. The machine in which your application is running is constrained by resources.
My answer to your question:
>how can I know if this memory accumulation leading to OOM is a Tomcat problem or a problem of the Java application that runs in Tomcat.
Most likely it is your application that seems to be the problem. To confirm capture heap dump from your application around 8 am time period and then analyze through heap dump analysis tools like heaphero.
Edit your Comment