Re: [Springframework-developer] CGLIB memory usage within class loader

[Seth L. <set...@gm...>]

On Tue, 19 Oct 2004 22:10:20 -0400, Guillaume Poirier
<gpo...@gl...> wrote:
> > How does it not create a leak if the classloader is not going away?
> > The real cause of the OOM exceptions is that the WebappClassLoader
> > instances never go away.
> 
> I meant if the container (e.g. Tomcat) doesn't throw the ClassLoader away,
> i.e. if it's still in use...
> Of course, if the webapp is reloaded and the old ClassLoader isn't
> collected, that's a leak.
> 
> What I was saying is the problem with Dom4j cause a leak when you reload the
> webapp,
> but cause no leak if you never use hot-reload.  (While the CGLIB leak
> apparently does the opposite)

Ahh... that's what I thought.  Thanks for the clarification!

I only wish A) there was a way to explicitly blow away the classloader
or B) have hibernate be redeployable.  One option is to place all the
Hibernate related classes inside Tomcat's shared Classloader.  This
might reduce the amount of times I need to restart.

Seth