DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3888>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3888 WebappClassLoader: Lifecycle error : CL stopped ------- Additional Comments From [EMAIL PROTECTED] 2002-10-11 07:39 ------- There there, Remy, hush now:) Now see what you've done Jon? You've made him upset! That won't help him fix the problem and we both want the problem fixed don't we?:) OK without the BS: I've talked a little with Remy over private mail yesterday, and with a friend of mine. In our server we'd forgotten to remove the examples webapp. If there ever was a webapp which causes problems it's that bugger. I removed it, and am getting a lot less errors. I still however did get some CL errors overnight... A lot less, but they still exist. Now here's a question for you Remy, I have no webapps left that are set to reloadable. Examples was the only one. You say this bug happens when a classloader is replaced by a new classloader. Why is the classloader replaced in the first place? Because of an attempt to conserve memory usage or something? Furthermore, I think Jon is correct to say that when the Classloader is stopped, it doesn't truly matter whether or not anything within this classloader had references to anything within this classloader itself. These references must be broken by VM. Otherwise the whole concept of the singleton (which has a static reference to an instance of itself) is an instant memory leak. So, if this holds true, it must mean, that something within a classloader holds a reference to something in another classloader (I think this is the point you're trying to make Remy?) Now, the only code I use from within my webapps, is the Servlet API classes, which is in the common classloader I believe, and I use a resource pool with mysql connections. However, I am fairly certain that I keep no connections open. Jon, you're getting this problem as well, do you use Tomcat's resource pooling? Maybe that's where we should start fishing. Anyway, let me know what you think about this novel I've just written:) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
