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=27434>. 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=27434 Deadlock with MultiThreadedHttpConnectionManager ------- Additional Comments From [EMAIL PROTECTED] 2004-03-04 16:04 ------- Deadlocks I've seen with MultiThreadedHttpConnectionManager are always due to a client that is not properly calling releaseConnection() on the requests. A few things to try - raise or lower the number of connections that it manages, and your deadlock will occur in a different place. That might tell you whether and where you are leaking connections. Was this working with a previous release (rc2, for example), and is only now broken? Can you describe/provide the code you're using to invoke HttpClient? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
