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=25370>. 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=25370 exception during writeRequest leaves the connection un-released ------- Additional Comments From [EMAIL PROTECTED] 2003-12-10 17:51 ------- > The statement "writeRequest method are supposed to be treated as > recoverable" appears to be false: the method signature has IOException in it Feel free to examine the source code and double-check. There is one situation I know of, when I/O exceptions would not be rethrown as HttpRecoverableException, that is, the connection is not known to have successfully completed a write operation at least once. In all other cases, I/O exceptions are rethrown as HttpRecoverableException (derived from IOException). > However, from the HTTP spec, a generic writeRequest is *not* simply > retriable (it is not considered idempotent for POST, PUT, etc; see > section 9.1 of the RFC). I would strongly discourage wrapping the IOException > inside writeRequest If understand the word of the spec correctly the section 9.1 postulates that "... methods can also have the property of "idempotence" in that ... the side-effects of N > 0 identical requests is the same as for a single request..." HttpClient never automatically re-executes requests on a read operation failure. Auto-recovery MAY takes place (if enabled) on a write operation (that is, the request body never makes it to the server in its entirety). That guarantees that there's at least one, but not more that one, successful request for a given resource. Feel free to correct me if I am missing something. Besides, auto-recovery can be customized through the use of MethodRetryHandler interface Again, any idea under what circumstances the reported problem occurs? Do you happen to know if CVS HEAD also exhibits the problem? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
