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=35944>. 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=35944 ------- Additional Comments From [EMAIL PROTECTED] 2005-08-01 17:29 ------- (In reply to comment #5) > So it is vitally important that the > releaseConnection call is in a finally clause. Please check your code for > ommissions of that. Yes, all method calls have their corresponding finally { method.releaseConnection(); } calls. I have my MTCM configured to just one connection per host, since that's all i need. We're talking about code that runs fine for hours and hours but then, inevitably, hangs in that wait(0) method. Well, maybe not "inevitably", but certainly whenever there's any kind of instability in the connection to the internet, which in my case seems to be inevitable. Hmm, but looking at the trace, that last page <http://humboldt.craigslist.org:80/sfo/eby/> leads you to a infinite redirect (blinking '/' <-> '//'). Could that be affecting the way the connection is closed? I see your point, my trace shows no call to HttpConnection.releaseConnection() but i can promise you that i've got a call to it (via the method) in my finally block. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
