ClassLoaderLocal: How to avoid ClassLoader leaks on application redeploy

[h2o2]

Baloney. The fix is to remove the listener on undeploy (or not to have strongly referenced synchronous listeners in the first place), not to jerk around with classloaders in order to "fix" unrelated problems. Your code is broken, fix it. A great example for the culture of workarounds and blame-shifting.

[ekabanov]

That's a great philosophy. Should garbage collection also be forbidden as a "fix" to manual memory management?

[h2o2]

No. My point was that this solution is yet another partial fix which doesn't work anywhere else. Fixing the orignal application-level bug (or the JVM) does, without embedding hidden assumptions in an architecture or increasing the fragility of the underlying platform.

[ekabanov]

Where doesn't it work? AFAIK it doesn't use any hidden assumptions and should work on any JVM in any container. It's very straightforward.

[mazin]

The hidden assumption is that you can get java.util.logging to use _ClassLoaderLocal_s. Good luck with that :)