The Java sockets classes did not provide any way to timeout the connect until JDK 1.4. Prior to that, only I/O after the connection was made was subject to timeout. The 2.3.1 release of SOAP does not support this new feature of JDK 1.4. However, the current code base does. If you download the code from http://cvs.apache.org/dist/soap/nightly/2004-06-22/, you will be able to have a shorter timeout for the connect if you are using JDK 1.4 or later.
Scott Nichol Do not send e-mail directly to this e-mail address, because it is filtered to accept only mail from specific mail lists. ----- Original Message ----- From: "Julien ALLANOS" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 20, 2004 8:32 AM Subject: timeout troubles Hello, I'm experiencing timeout using ws-soap-2.3.1: if i try to invocate a soap method in my client, using a wrong ip address, call.invoke() throws an exception (java.net.ConnectException: Connection timed out) after 3-4 minutes. I want to lower this timeout delay, but i believe Call.setTimeout() and SOAPHTTPConnection.setTimeout() methods are only used once the connection on the IP layer is established. Any hint please? Btw, what is the difference between Call timeout and SOAPHTTPConnection timeout? Thanks for feedback. -- Julien ALLANOS Silicomp-AQL
