Just out of curiosity, do you have a } catch(Throwable) { in your code?
Probably in an action, or even in your ClassLoader code?
If so, if you don't } catch(ThreadDeath) { and re-throw it, you will indeed
cause a memory leak very similar to the one you describe.
Java internally uses the ThreadDe
Hello everyone,
it seems that resin 4.0.23 suffers from a classloader leak.
My application's classloader is prevented from being garbage collected.
Please have a look at the GC Roots of my applications classloader
(after stopping the application and a full garbage collection):
Class Name
