2016-08-23 17:55 GMT+02:00 Clebert Suconic <[email protected]>:
> > Not always. Will be true until something else has a reference to the > > classloader, like a provider Class for instance. > > In other words it can just prevent the whole webapp to be garbage > collected. > > A provider class Is not supposed to hold an explicit reference to the > classLoader. > Just the fact to load a Class does, at least on some JVM (yes it hurts) > > That would be an implementation bug. If the provider is holding a > classLoader reference it would prevent the GC on the WAR / > redeployment no matter what. > > I can write a testcase preventing issues. I had written one for > commons a few years ago. > > > > What is your other solution? > > > Either what was there (I know), eviction thread (I know too) or server integration (I'm fine with that) > > > What is your other solution? > Once again "registry" is ok again to start
