db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg von Frantzius <joerg.von.frantz...@artnology.com>
Subject Re: classes registered in JDOImplHelper unloaded
Date Mon, 06 Mar 2006 16:36:40 GMT
Holding strong references to class objects will also prevent any 
hot-deployment mechanisms in application servers from working. Finally I 
learned why it never worked for us ;)

Erik Bengtson schrieb:
> Let me rewrite in English ;)
>
> Hi,
>
> If applications using short lived classloaders register PC classes, and later on
> these classloaders are released. Classes should be GC together with the
> classloaders, but the JDOImplHelper is holding strong references to these
> classes.
>
> What is the strategy to take to avoid a memory leak in JDOImplHelper?
>
> Regards,
>
> Quoting Erik Bengtson <erik@jpox.org>:
>
>   
>> Hi,
>>
>> What happens if the classes registered in a JDOImplHelper are unloaded or if
>> an
>> attempt to GC the classloader?
>>
>> Later on the same class loaded by a second classloader, third, forth and so
>> on?
>>
>> Is there a memory leak here since the classloader will not be garbage collect
>> the classes as we have a strong references to the classes?
>>
>> Regards,
>>
>> Erik Bengtson
>>
>>     
>
>
>
>
>
>   


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message