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