I enabled our JVM to store a heap dump in case of another memory error Therefore we decided to need a heap dump to finally localize the cause of the problem. Decision makingĪfter some internal meetings, we guessed that the problem must be some case of the hashmap, caching, or similar. Certainly not!Īnalyzing several of our monitoring and logging tools wasn’t very revealing either. So I’m pretty sure our code is always bug-free, as it is in any software development team. Of course not, because we implement a pretty good review process that prevents any problems. To share some insight on how I handled and localized the issue, this post summarizes some basics to discover possible memory leaks using Eclipse Memory Analyzer.Īfter a quick search of our recent major commits, I couldn’t find any change that would cause a heap problem. Of course, this is one of the most shocking log entries for any developer. Recently I was informed about some : Java heap space issue found in one of our application logs.
0 Comments
Leave a Reply. |