Hi,
This is my 1st message to the list.
I have created a web app, integrated with a web server called Jetty. Both of them use commons-logging 1.5 alpha1. There is just one set of jars shared between them. The optional package is included, so weak references must be active.
I have implemente webapp reload, by throwing the old class loader and creating a new one.
I have observed with the help of a memory profiler, that the old class loader isn't memory garbaged.
The cause is the log references. The garbage roots are that maintain live references are:
* static HIERARCHY in org.apache.log.Hierarchy
* static log in org.mortbay.util.URLResource and some other Jetty
classes that use Commons Logging.
I have tested under Java 1.5.0.03 in Windows XP.
Can someone please give me some indications?
Is it best to have separate commons-logging instances between my web app and the web server?
Best regards David P�rez
