You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-dev@ws.apache.org by bu...@apache.org on 2003/05/29 23:38:03 UTC
DO NOT REPLY [Bug 20339] New: -
LiteXmlRpcTransport throws IOExcpetion 'socket closed'
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=20339>.
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=20339
LiteXmlRpcTransport throws IOExcpetion 'socket closed'
Summary: LiteXmlRpcTransport throws IOExcpetion 'socket closed'
Product: XML-RPC
Version: 1.2
Platform: All
OS/Version: All
Status: NEW
Severity: Major
Priority: Other
Component: Source
AssignedTo: rpc-dev@xml.apache.org
ReportedBy: spencer@proffit.net
When receiveing a response that isn't loaded into the input stream buffer, you
will get an IOException caused by socket closed.
This is caused in sendXmlRpc where closeConnection is called (unless keepalive
is on) before 'in' is returned. This means that 'close' is called on the socket
before the caller of 'sendXmlRpc' ever gets the InputStream. If the response is
already loaded in the BufferedInputStream there is no problem, but for slower,
larger responses, you will get the Exception.