Re: [Springframework-developer] CachedIntrospectionResults classCache leak

[<jue...@we...>]

If this happens with Spring 1.0.2, it is typically caused by *other* =
code that causes a leak. The ClassLoader is then still around, also =
showing Spring classes like CachedIntrospectionResults. This is not =
Spring's fault: Spring classes just keep hanging around as a side =
effect.
=20
Try calling "java.beans.Introspector.flushCaches()" on application =
shutdown. This is a typical source of such leaks: The JavaBeans =
Introspector might still refer to application classes. This is not =
caused by Spring: It's rather other libraries that use the Introspector, =
for example Quartz.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Rod Johnson
Gesendet: Do 15.07.2004 14:38
An: spr...@li...
Betreff: Re: [Springframework-developer] CachedIntrospectionResults =
classCache leak



Claudio

What version of Spring is your analysis against?

R

----- Original Message -----
From: "Claudio D'Angelo" <cla...@ob...>
To: <spr...@li...>
Sent: Thursday, July 15, 2004 10:26 AM
Subject: [Springframework-developer] CachedIntrospectionResults =
classCache
leak


> Hi,
> I'm analyzing with OptimizeIt my web application:
> when I redeploy the application I note that instances of
> CachedIntrospectionResults still in memory and for any redeploy the
> instances raise.




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=3D4721&alloc_id=3D10040&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer