> Hi,
>
> I have been bothered by a time-out issue for quite a few days and wonder
> if I can get some help from the mailing list.
>
> We have a Axis 1.1 client application that connects to a remote Web
> Service written also in Axis 1.1. The application almost always receives
> response in all computers excepts one. In that one particular computer,
> most time it gets SocketTimeoutException as reported widely in Internet:
>
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: java.net.SocketTimeoutException: Read timed out
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace: java.net.SocketTimeoutException:
> Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(Unknown Source)
> ...
>
> The only answer I found so far is to increase the timeout value (more than
> 60 seconds) of the binding stub. That didn't work for us.
>
> However, the application gets response sometimes (about 5% of all the
> times we tried) without any change.
>
> This convinced me that this might be a computer configuration issue. It
> has same general configuration as another computer that worked -- Windows
> 2000, dynamic IP, on the same network.
>
> Somebody would have some clue?
>
> Thanks!
> Yu Feng
<<attachment: winmail.dat>>
