[ http://issues.apache.org/jira/browse/XMLRPC-112?page=comments#action_12441687 ] Jochen Wiedmann commented on XMLRPC-112: ----------------------------------------
> Which version did you test it against? Is this from the latest SVN sources? Yes, of course. See 3.1-SNAPSHOT on http://people.apache.org/dist/ws/xmlrpc/nightly/ > XmlRpcClient executeAsync() causes failures for subsequent execute() > -------------------------------------------------------------------- > > Key: XMLRPC-112 > URL: http://issues.apache.org/jira/browse/XMLRPC-112 > Project: XML-RPC > Issue Type: Bug > Components: Releases > Affects Versions: 3.0 > Environment: Mac OS X 10.4 on the Client > Reporter: Alastair Tse > Attachments: XmlRpcAsync.java, XmlRpcAsync.java > > > I'm currently using Apache WS XML-RPC 3.0 and I think I might have stumbled > across a bug regarding using executeAsync() and execute() in the same client. > Basically, I have an XMLRPC client which I would like to use synchronous > calls and some with asynchronous, however, as soon as I start using > executeAsync(), all the subsequent execute() will start to fail. > The XML-RPC server is a Python SimpleXMLRPCServer. I've also tested it with > the twisted.web XMLRPC implementation as well. I did some further > investigating and found that the executeAsync call was sending a > "Content-Length: 0" with no corresponding XMLRPC request to the server, > causing an HTTP 500 response from the server. > From ngrep, the HTTP headers look something like this: > T 192.168.9.3:50335 -> XX.XXX.XXX.XX:8999 [AP] > POST / HTTP/1.1..Content-Type: text/xml..User-Agent: Apache XML RPC 3.0 (Su > n HTTP Transport)..Content-Length: 0..Cache-Control: no-cache..Pragma: no-c > ache..Host: XX.XXX.XXX.XX:8999..Accept: text/html, image/gif, i > mage/jpeg, *; q=.2, */*; q=.2..Connection: keep-alive.... > ## > T XX.XXX.XXX.XX:8999 -> 192.168.9.3:50335 [AP] > HTTP/1.0 500 Internal error.. > ## > Attached is an example client that produces an error. Change the execute call > to a function on an echo XMLRPC server. > It would be great to know if it is my fault, or something funny going on with > the threading inside XMLRPC. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
