Mostly we do not encounter this error in preliminary stages of application development. Sometimes functional testing reveals this error, but many times it is revealed during performance testing. It is not so annoying when it occurs before we push the application into production, but the real pain starts when we are hit by this error in production. When production server goes down or hangs itself with java.lang.OutOfMemoryError, it can even lead to a heavy monitory loss.

Garbage collection, something not to worry, sometime to worry a lot. A novice Java developer starts writing first code without worrying a bit about memory utilized by the program. There is always this, I would say wrong notion, that garbage collector is there to clean up any memory consumed. But when the application runs out of memory, then the developer starts cursing Java for in-efficient memory management. Is Java the culprit? Or it is the memory consumption by the program is problem. In this article we identify ten important points, …