Stephen Duncan wrote:
Also look at the second question in this FAQ:
http://tomcat.apache.org/faq/deployment.html
It explains why reloading an app causes this problem to show up more quickly.
The description sounds like it would apply to any container that uses
multiple classloaders, not just Tomcat, so it's likely true for Jetty
as well.
That would explain it. I wonder why the
difficulty with releasing unreferenced
class loaders.
-dub
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
