Hi, >But hey, I thought one of the big selling points is that Java DOES NOT >LEAK! >Am I mistaken? Isn't it's absence of pointers its big plus? If it does leak >then changing the heap size is going to be irrelevant. No matter how large >you set it it will bite you in the bum eventually!
;( You're mistaken unfortunately, and what's worse is that you're not alone by far. Java by itself doesn't leak, but it's not hard to write code that unintentionally keeps references to objects. Here are some references, but the topic is easy to find on Google or various Java forums: http://www-106.ibm.com/developerworks/java/library/j-leaks/ http://www.adtmag.com/java/articleold.asp?id=165 http://sys-con.com/story/?storyid=44716&DE=1 http://www.theserverside.com/articles/content/J2EEPerformance/Eliminatin g_memory_leaks.html http://www.hp.com/products1/unix/java/infolibrary/prog_guide/diag_memory _leaks.html It goes on and on... I've given examples on this list in the past of some common servlet-related leaks too. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
