Tom Cook wrote:
> On Fri, 16 Feb 2001, you wrote:
> > Strange, but it looks like these
> > classloaders are never removed from
> > the web server again on undeployment.
> > In fact, it looks to me like currently
> > classloaders are *never* removed from
> > the webserver.
> > That looks like a bug to me: It means
> > that the classloaders for old containers
> > are never freed, and that the old
> > classes of the jar might still be
> > served (maybe not if the jars these
> > classloaders use have been overwritten
> > or removed).
> > At least the webserver's list of
> > classloaders will continue to grow at
> > every deployment and redeployment.
> > Unless someone comes up with an
> > explanation, I'll better have a closer
> > look and possibly raise this on the
> > jboss-dev list.
>
> You could just make the webserver use weak references. Then the classloader
> will be kept until it is no longer in use in other places, then it will be
> garbage collected despite the webserver's weak reference to it.
The right thing to do would probably be to
have the deployer remove the classloader
from the web server again on undeployment.
The method for this is already present in
the webserver, it is just never called.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
