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=25592>. 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=25592 An IOException or RuntimeException leaves the underlying socket in an undetermined state Summary: An IOException or RuntimeException leaves the underlying socket in an undetermined state Product: Commons Version: 2.0 Beta 2 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: HttpClient AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If an application level IOException or RuntimeException occurs, the underlying socket will be in an undetermined state. In many cases, this will lead to zombie connections in the pool that do not respond properly. Simple example: uploading a file via POST. If we promise the server 1MB of data. Shortly after starting the transfer an IOException occurs (e.g. the NFS server the file was residing on stops responding). The connection is returned to the pool (see bug #25370) but the the server is still expecting close to 1MB of data on that socket. The next request on that socket (e.g. a GET) will send the HTTP header but the server thinks the header is part of the old stream and doesn't respond. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
