Hello Craig,
I second Hybris on this.
I ran into the same problem as you when I started using this library.
I think the problem is that the transport factory you are using DOES
NOT honor your timeout setting in XmlRpcClientConfig because it's
simply not implemented.
Unfortunately, I don't remember by heart which one does or doesn't.
They are listed here:
http://ws.apache.org/xmlrpc/client.html
You may check the code.
--
Sometimes ago, I noted that the version 3.x of this library started
to be very difficult to grasp for new user. I ran into many problems
when I switched from v2 to v3. I wrote that I felt it's against the
xmlrpc philosophy, but my post didn't get much echo.
I guess it's fair since the primary users of this library are the
ones developing it.
IMHO, v3 wanted to become more generic (we always say, it's better)
but lost pragmatism in the development. Now, we you set Reply or
Connection timeouts, you must be aware that your current transport
might or might not use the setting... You will then lose a lot of
valuable time "debugging" your ignorance...
Anyway, I believe v2 or maybe the RedStone library (http://
xmlrpc.sourceforge.net/ that I'll try next time I need to implement
xmlrpc) are better choices if you only need to do simple stuff with
xmlrpc.
Best Regards,
Gam.
On 10 Oct 2008, at 10:36, Craig Spry wrote:
Hello List,
Just to give you an update, I've tried xmlrpc-client-3.1.1,
configuring it this way:
XmlRpcClientConfigImpl config = new XmlRpcClientConfigImpl();
config.setServerURL(url);
config.setReplyTimeout(60000);
config.setConnectionTimeout(60000);
_client = new XmlRpcClient();
_client.setConfig(config);
And I still get the same result.
Thanks,
Craig
-----Original Message-----
From: Craig Spry [mailto:[EMAIL PROTECTED]
Sent: Friday, 10 October 2008 10:33 AM
To: [email protected]
Subject: XML RPC call hangs
Hello List,
I'm using xmlrpc-client-3.0 calling a XML RPC method on apache
running on windows. When I make a certain call it causes apache to
hang on the windows machine. Now I have my XML RPC client
configured like this:
XmlRpcClientConfigImpl config = new XmlRpcClientConfigImpl();
config.setServerURL(url);
config.setReplyTimeout(60000);
_client = new XmlRpcClient();
_client.setConfig(config);
Now I would expect that when this call hangs the client should wait
around for 60 seconds then throw an exception, but instead it waits
around until I restart the apache server. Is there a way to
configure the client to not hang when the server does?
Thanks
Craig Spry
If you are not an authorised recipient of this e-mail, please
contact me at Redflex immediately by return phone call or by email.
In this case, you should not read, print, retransmit, store or act
in reliance on this e-mail or any attachments, and should destroy
all copies of them. This e-mail and any attachments are
confidential and may contain privileged information and/or
copyright material of Redflex or third parties. You should only
retransmit, distribute or commercialise the material if you are
authorised to do so. This notice should not be removed.
If you are not an authorised recipient of this e-mail, please
contact me at Redflex immediately by return phone call or by email.
In this case, you should not read, print, retransmit, store or act
in reliance on this e-mail or any attachments, and should destroy
all copies of them. This e-mail and any attachments are
confidential and may contain privileged information and/or
copyright material of Redflex or third parties. You should only
retransmit, distribute or commercialise the material if you are
authorised to do so. This notice should not be removed.
