DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28291>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28291 ------- Additional Comments From [EMAIL PROTECTED] 2005-03-17 18:51 ------- When running on Tomcat, the container should call release on the instance loaded in the shared library after each classloader is deployed. This is why I made this suggestion. It's hard to know whether the classloader will get collected upon hot deployment even when LogFactory is defined by the child classloader on all platforms (which is why I caveated my answers). Garbage collection and reflection has had some wrinkles (and bugs). I wouldn't be surprised if it didn't on some (but would bet on it). The way that I would have proceeded would have been to set a hot deployment test for my particular application to determine whether there is a detectable memory leak. (I believe that this is how the tomcat problems were first recognized.) However, Chris asked for a therotical answer so I did my best. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
