This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
In splitloaders, TopManager.systemClassLoader is a dynamic call that can change after a module uninstall or reinstall. But something in httpserver seems to keep a strong reference to the systemClassLoader that existed when httpserver was loaded, which can have bad effects on module reinstallation, as well as being a potential memory leak. I think NbServletsInterceptor.java line 35 is to blame, but I am not sure. The reference seems to be via some servlet mapping.
Version: 'Dev' -> 3.2
Target milestone -> 3.3
assigned
Target milestone 3.3.1.
see 18613
HttpServerModule.ContextReloader seems to be doing this. I can't really verify since I have no recollection of how I found out that the systemClassLoader was being retained. Could perhaps verify better by creating a module with an internal servlet, then reloading it in test mode repeatedly (running it each time), ensuring that changes to the code are honored, and using -J-Dorg.netbeans.core.modules=0 to check that each time the class loader for the module is reclaimed reliably at some point after it is uninstalled. I don't really have the time to do this; maybe someone from QA would like to.
In issue #18613, verified that reloading the module uses the new servlet code. So this is very likely fixed as well, but not directly confirmed.
Resolved for 3.3.x or earlier, no new info since then -> closing.