mail lists.
- Original Message -
From: "Julien ALLANOS" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 20, 2004 11:21 AM
Subject: Re: timeout troubles
Selon Scott Nichol <[EMAIL PROTECTED]>:
> The Java sockets classes did not provide any w
Selon Scott Nichol <[EMAIL PROTECTED]>:
> 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, t
.
- 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 clien
ulien 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.i
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()
