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=23703>. 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=23703 Freezes w/ MultiThreadedHttpConnectionManager ------- Additional Comments From [EMAIL PROTECTED] 2003-10-10 07:39 ------- Adam, There are two layers of code on top of the HttpClient (both I know very little of), so it is really difficult for me to make any soft of informed guesses about a possible cause of the problem. But what I can see from the logs and the code snippets makes me fairly confident about a few things: * I do not see connection being released in the log. I do not why this happens but this is what I see. * In VFS the connection release is supposed to be triggered by closing the input stream. The consumer of the VFS code must ensure that the input stream is closed under all circumstances (including abnormal circumstances). * Please consider downgrading to HttpClient 2.0. CVS HEAD is currently in a state of flux and should be considered experimental. * I can well imagine that there is a bug in the multi-threaded connection manager code that is triggered by some sort of less usual combination of an HTTP HEAD followed by 301, or probably non-compliant HTTP HEAD (that returns a body) followed by 301. But unless the issue is isolated and is reproduceable with a smaller, more manageable test case, it is really hard to tell Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
