Hello! I've come across a problem in the way connection failures are handled. My code sets up a SOAP http connection object, sets a timeout for it and sets the call's setSOAPtransport to it. However, if the target of the call is off the network (I pulled the plug for testing), the call.invoke waits 100 seconds (regardless of what timeout I set) and then times out with a SOAPException.
In looking at the SOAP code (I downloaded the nightly source), it looks like the socket connect is being done at socket constructor time with a constructor that does not allow a timeout parameter. Thus, if the connect is going to fail it will fail at the default timeout time. I think what we want here is for the socket to be constructed (without the connection parameters) and then connected using the connect call and our timeout parameter. Comments? mike. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
