Troubleshooting Memory Problems in Java Applications

Poonam Parhar, Consulting Member of Technical Staff, Oracle
Troubleshooting memory problems can be tricky, but the right approach and proper set of tools can simplify the process substantially. Several kinds of OutOfMemoryError messages can be reported by the Java HotSpot VM, and it is important to understand these error messages clearly and have a wide range of diagnostic and troubleshooting tools in our toolkit to diagnose and root out these problems. This session discusses the right approach and a broad range of diagnostic tools that can be very useful in troubleshooting Java memory issues.

[@dasikalyan]

Nuggets of gold. If anyone is dealing with a memory leak issue in a JVM, this video is a god send. Thank you Poonam for sharing your knowledge. With the tools mentioned in the video and the steps to debug and interpret the reports, we were able to link it a memory leak that was fixed in the spring-retry library. Thank you so much once again.

[@eduardocucharro]

Great content. Thank you!

[@debabrata98]

Glad I found this video. Thank you 🙏🏽

[@kirillnovik8661]

JavaOne RockStar!

[@soumyavuppala5744]

Absolutely great presentation 👍🏻

[@java]

Glad you liked it!

[@BangaloreJUG]

Nice presentation...

[@005kapil]

I wonder can this all be really possible to manage by the developer? This is some thing which may look easy but pretty difficult when arises in real time. Could there be not some better way to make it more easier not just to understand theoretical but so solve real issues? It was a good video session but I'm thinking how much I can really take home and use it when problem comes...??

[@berndeckenfels]

005kapil there are commercial tools like ibmsupport assist or jclarity, some apm tools can also monitor vm. But generally It's complicated and requires experience in the presence of bad code.

[@siddharthpandey8516]

same thoughts here

[@parthapal8380]

OOM is an error and not an exception , exceptions are recoverable while errors are not ,not sure why it was being mentioned as OOM error exception overall a good presentation

[@stokitko]

You can catch OOM and even recover system from it, e.g. temporary stop processing and call System.gc() explicitly and then everything will be fine. Take a look on LowMemory class from Apache Derby

[@berndeckenfels]

Sergey Ponomarev you can catch (OOM) errors, but it is very dangerous as they can have corrupted internal state. So typically restarting ASAP is adviceable

[@pulakkhearu7260]

Can you share your Any blogs where i will find in depth knowledge about oacore servers?

[@truthiwillsay1863]

From where we can collect GC logs

[@venkateshrasipuram4804]

Does metaspace part of heap or non-heap?? If it's non-heap then how it claims the space by Full GCs??

[@karthickshanmugam5388]

not part of heap memory

[@srikanthuppala8297]

Content & presentation is good. My minor suggestion would be avoid/reduce "Aaaa Aaaa" sounds while in the meeting.

[@angelgoncalves2295]

When my boss asks me to explain why my Java app throws an OOM 18:54

[@maddukurimanikanta1981]

lol