axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yu Feng" <>
Subject RE: Question on timeout
Date Thu, 16 Dec 2004 16:05:40 GMT
Two questions on TCPMon.

If I originally wants to connect to, when I use TcpMon, is this how I
should use: set listening port 5050, target host and target port
443, and change my request to http://localhost:5050/Axis/DownloadService?

Second question, I noticed something different when I use Axis1.1 or Axis1.2
to start TcpMon:

With above setting (assuming it's correct), with Axis 1.1, I can see connect
to in Request panel; however, with Axis 1.2, it says connecting
to, is this a bug in Axis 1.2? It really should be if port is shown as well.


-----Original Message-----
From: Elaine Nance []
Sent: Tuesday, December 14, 2004 5:37 PM
Subject: Re: Question on timeout

Maybe the timeout settings?  or set up TCPMonitor and see whats
going back and forth.

Yu Feng wrote:

> Thanks for help!
> The computer where this connection problem occurs is our application
> so I haven't got a chance to replace network card. However, it runs all
> other non-Axis applications ok that require Internet connection.
> The exact SocketTimeoutException problem also happened in the computers
> I said "almost always receives response" -- but very rarely and I couldn't
> recreate it if I aim to. So somehow I think that application server
> just had worse network configuration that couldn't survive a query most
> time. I am wondering if there're some software aspect approach I can look
> into?
> I once heard about TCP_NODELAY setup in registry, but apparently there're
> such setting in any computers here.
> Yu Feng
> -----Original Message-----
> From: Elaine Nance []
> Sent: Tuesday, December 14, 2004 2:44 PM
> To:
> Subject: Re: Question on timeout
> I would bet that the Network Interface Card (NIC) is not working
> properly, if it is an issue only for one computer.  Or that the
> patch cord for the computer is bad, for example if someone
> tripped over it, and so on.
> Yu Feng wrote:
>>>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:
>>>faultString: Read timed out
>>>Read timed out
>>>at Method)
>>>at Source)
>>>The only answer I found so far is to increase the timeout value (more
>>>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?
>>>Yu Feng
> --
> <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   |  Computers are useless. They can only give you answers.
>   |                                 --  Pablo Picasso  --
> <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  |  Computers are useless. They can only give you answers.
  |                                 --  Pablo Picasso  --

View raw message