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=20718>. 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=20718 uninformative exceptions ------- Additional Comments From [EMAIL PROTECTED] 2003-08-12 12:28 ------- This can happen when the server does a socket.close() before writing a reply. For instance, in tomcat, this happens if you configure a given number of processors for the webapp, and then it receives more concurrent exceptions than this. On the client side, in the HTTPSender.readFromSocket() code, it will then receive an '0' return code, since it isn't set, and create a fault, like the one you see. Perhaps doing better error handling in the case of getting a '0' return code, or no bytes returned would help this. Is this a worthwhile change? If so, I'm willing to code it up. cheers, james.
