Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 18232 invoked from network); 16 Feb 2005 20:30:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 16 Feb 2005 20:30:18 -0000 Received: (qmail 94412 invoked by uid 500); 16 Feb 2005 20:30:15 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 94332 invoked by uid 500); 16 Feb 2005 20:30:15 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 94308 invoked by uid 99); 16 Feb 2005 20:30:15 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of robertburrelldonkin@blueyonder.co.uk designates 195.188.213.4 as permitted sender) Received: from smtp-out1.blueyonder.co.uk (HELO smtp-out1.blueyonder.co.uk) (195.188.213.4) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 16 Feb 2005 12:30:12 -0800 Received: from [10.0.0.7] ([82.38.65.173]) by smtp-out1.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Wed, 16 Feb 2005 20:30:44 +0000 Subject: Re: jcl blog post From: robert burrell donkin To: Jakarta Commons Developers List In-Reply-To: References: Content-Type: text/plain Message-Id: <1108586040.2411.32.camel@knossos.elmet> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6-2.1.92mdk Date: Wed, 16 Feb 2005 20:34:00 +0000 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Feb 2005 20:30:44.0727 (UTC) FILETIME=[64062070:01C51466] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N FWIW this is a well known issue with JCL and there's no way to cure it on 1.2 JVMs (which was the target for JCL). (thanks to brian) for a few months now, HEAD has had compatible code which allows memory reclamation on more modern JVMs (with weak references). if a few more folks were prepared to test the release candidate, this code might even get a release... it's only a practical issue in containers which have JCL placed into a classloader high in the tree and then hot deploy contained applications without calling release. it is also documented in the javadocs (which should help to explain why it took so long for users to discover this limitation.) at least ceki puts time and effort into researching his critiques... - robert On Wed, 2005-02-16 at 04:50, Vic wrote: > oops :-[ > Wrong link, this is it: > http://www.szegedi.org/articles/memleak.html > > It talks about Commons logging, since i'ts open season. > .V > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org