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=24560>. 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=24560 HttpClient loops endlessly while trying to retrieve status line ------- Additional Comments From [EMAIL PROTECTED] 2003-12-10 13:17 ------- > in fact, this checked exception is caught and simply logged with LOG.error > (see patched HttpMethodBase.responseBodyConsumed()). Christian, Unfortunately I can't agree that this is just a matter of ignoring the said checked exception. The problem is that there's no (or I personally do not know of a) reliable way to tell if the I/O exception is thrown due to a closed socket or due to a communication error. The former can be safely ignored but the latter cannot. Unless you know how to resolve this problem without resorting error message parsing, I persnally would rather see this check removed altogether. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
