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=24309>. 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=24309 MultiThreadedHttpConnectionManager daemon Thread never GC'd ------- Additional Comments From [EMAIL PROTECTED] 2003-11-02 23:34 ------- Mike, Alas, due to craziness in my schedule, I'll not have a chance to look at this more closely until late Monday or Tuesday at the earliest. One suggestion, though, is that I'd like to see a test case. The test case could wrap each of the connection manager, and possibly the HostConfiguration with a WeakReference, and then after forcing a gc, make sure that the references are null. That the MultiThreadedHttpConnectionManager was never garbage collected was our first indication that something was awry.... My patch that put a name on the ReferenceQueueThread. I did that so that it is easier to identify (and, for the most part, ignore) in a debugger. I'm hoping any change to fix this bug will include that. I like the idea of a single monitor thread! Thanks for looking at this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
