ws-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mauro Canal" <>
Subject RE: looong connection timeout if server down
Date Wed, 22 Jan 2003 13:28:36 GMT
Hello Jason

the timeout problem comes from the insufficient implementation
within the URLConnection class used in DefaultXmlRpcTransport.

there are two solutions for your problem:
1. execute the request in a thread for the XmlRpcClient and
   check the timeout.
2. create an own XmlRpcTransport implementation using the HttpClient from
   This client implements the timeout functionality.
   Take a look on the DefaultXmlRpcTransport class how to implement the

Mauro Canal

-----Original Message-----
From: Jason Wyatt []
Sent: Wednesday, January 22, 2003 8:30 AM
Subject: looong connection timeout if server down


I used XML-RPC on a project recently and it was pretty good, except I had a
problem with a very long timeout if the server went down. It seems the
timeout was quick when we were developing under Windows (~30seconds) but
when we deployed to Solaris the timeout was around 3-4 minutes.This was a
bit of a problem because our client's remote devices which run the XML-RPC
server may or may not be available at any given time.

We considered changing the kernel socket connect timeout settings on the
XML-RPC client machine, but this seemed like a risky option as it could
adversely affect other internet services. I had a look at hacking the
XML_RPC client but gave up once I got down to http and couldn't see an
obvious connect timeout setting.

Is there an easy programmatic way of changing the connection timeout that I
am missing here? I would seriously like to use XML-PRC again on a new
project, but the socket timeout issue is a vote against it.

Any help with this would be kindly appreciated.

Thanks in advance,

 Itree Software
 Ph (02)42263454        Fax (02)42263193
        -> Meeting your requirements.
        -> Delivering on promises.
        -> Pride in our work.

View raw message