Solving OutOfMemoryError (part 1) – story of a developer
Another day in the office. Except that you get another call from the operations saying they now have to restart your production application every three hours. And they seem to be somewhat annoyed with this. You have a feeling that their emotion is in correlation to the number of phone calls customer support is getting lately – which has skyrocketed in the past few weeks.
I’m sure you have been there. And I am also sure you wish you would never have to be there again.
All you have is a symptom: an OutOfMemoryError. You have no clue what causes it. You cannot reproduce the problem. You cannot see the log files in production. But you have to solve it. Not that you have the task in your job contract – you are just a developer – the reasons are rather related to your engineering pride and being a responsible human being.
Did you know that 20% of Java applications have memory leaks? Don’t kill your application – instead find and fix leaks with Plumbr in minutes.
And here we go again. Sleepless nights or weeks. Struggling with authorization issues and bureaucracy. Getting ignorant people find the correct data for you. Great. Just great. Having the boss breathe down on your neck does not help much either. “When will it be fixed?” I bet you’d rather estimate when the P versus NP problem will be solved.
In this blog we are planning to write about everything related to the situations described above. The next posts will concentrate on how these situations are currently handled, what tools and techniques are popularly used and how you can benefit from them when in a similar situation. As we are a product development company, we might mention our own solutions somewhere along the way, but we promise it will be an interesting read nonetheless! The later blog posts in the series (thus far) include:
Wait… why isn’t it the developer’s reponsibility to fix their app? If not the dev then who?
lol.. every three hours? Bad application….lollll
Looking forward to the next posts 🙂