|
|
Re: Memory Leaks in J2EE Apps
|
Posted: Mar 17, 2006 6:36 AM
|
|
Using java (and other other VM oriented platforms) we often forget important memory and resource management issues.
I think that the problem is more general: resource leaks in managed virtual machine.
Unknown or unwanted object references cause memory leaks AND resource leaks.
In a distributed system, resources like the bandwith used by a connection may weights more than the effective allocated memory.
The article raises an important question: a wrong use of design patterns may increase memory/resource leaks.
I disagree with this quote:
"... explicitly cleaning the heap may be a mandatory programming requirement in some applications; doing so must be considered on a case-by-case basis"
If cleaning the heap means to call System.gc(), this is a fairy tale. Artima docet: "System.gc() Is a Suggestion, not a Command",
http://www.artima.com/legacy/design/cleanup/messages/36.html
Last personal consideration: this is a little loss of "don't care of memory management" philosophy.
|
|
Previous Topic
