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-04 16:40 ------- I inspected the code carefully, and didn't see any issues, so I'm happy with the second patch that Mike submitted. Hopefully neither of us missed anything! On a slightly unrelated note, it occurs to me that the logic of MultiThreadedHttpConnectionManager.removeReferenceToConnection() would be a lot simpler if the HttpConnection could optionally provide a weak reference to itself, so that the "remove" process was a simple get on the weakref to the connection. Mind you, if clients are using "releaseConnection" properly, the performance difference would be miniscule, but might matter slightly more with many instances of the connection manager. Too many ideas, too little time.... Whatever - I don't know as the above change is useful, it was just a thought that occurred to me. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
