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=27589>. 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=27589 MultiThreadedConnectionManager should provide a shutdown ------- Additional Comments From [EMAIL PROTECTED] 2004-03-12 15:38 ------- This is a MUST HAVE feature. It is causing a resource leak in our server software that is going to force us to not use this library. If thread A makes a blocking IO HTTP request on a host, then thread B needs to be able to call Socket.close(), forcing an IO Exception on thread A so it wakes up from a blocking Socket.read() call. IS there any workaround that would let us do it NOW? Could you suggest how I could modify my own version of the code to do it? URGENTLY NEEDED. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
