Received: by 10.66.84.202 with SMTP id b10mr8134267paz.43.1352756125777; Mon, 12 Nov 2012 13:35:25 -0800 (PST) Received: by 10.68.251.196 with SMTP id zm4mr5777515pbc.4.1352756125723; Mon, 12 Nov 2012 13:35:25 -0800 (PST) Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!kr7no6700113pbb.0!news-out.google.com!s9ni5145pbb.0!nntp.google.com!kt20no6404549pbb.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.java.programmer Date: Mon, 12 Nov 2012 13:35:25 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.28.149.29; posting-account=CP-lKQoAAAAGtB5diOuGlDQk0jIwmH0T NNTP-Posting-Host: 69.28.149.29 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Java daemon From: Lew Injection-Date: Mon, 12 Nov 2012 21:35:25 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: csiph.com comp.lang.java.programmer:19719 Jim Janney wrote: > "sl@exabyte" writes: >> I gather that PHP daemon suffers from memory leak problem due to its garbage >> collector mechanism. More likely it suffers from a packratting problem - failure to release memory. >> Since java also adopts the garbage collector mechanism, would java daemon >> suffers from the same memory problem ? Not the same problem, but you can force Java to hang on to object references long past their usefulness, and eventually use up your available memory. Idiomatic Java avoids this. -- Lew