commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <robertburrelldon...@blueyonder.co.uk>
Subject Re: jcl blog post
Date Wed, 16 Feb 2005 20:34:00 GMT
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
> 
> <http://www.boardVU.com>
> 
> 
> ---------------------------------------------------------------------
> 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


Mime
View raw message