The reply timeout set in the XmlRpcHttpClientConfig is ignored when making synchronous calls from the client. This may cause calls to hang forever if there is no response.
Digging into the code, I noticed that the read timeout provided by the XmlRpcHttpClientConfig is ignored when creating a URLConnection from the XmlRpcSunHttpTransport. The method URLConnection.setReadTimeout, made available in Java 1.5, could be used to solve this. Is this a bug or is it a deliberate choice you've made to keep Java 1.4 compatibility? Thanks Lars Gråmark
