RE: Long Delays Interacting With Server



W,

I just posted a question regarding a problem that sounds vaguely similar.

Regarding the problem you describe, have you captured network traces at both
the server AND the client (before/as either hits the wire)? At a minimum,
you should capture at both points and compare to make sure there is no
evidence of dropped packets.

If you have the results of both captures and want to post them (like you
summarized below, but adding at least the timestamps), the community can help
you decipher any clues present.

"W" wrote:

I have an application server at one office that I use from another. Just
the last few days the application is introducing long delays. In looking
at the sniffer trace, what I see is a typical interaction like this:

ClientPort > ServerPort [ACK] Seq=298 Ack=13604 Win=64512 Len=0
ServerPort > ClientPort [ACK] Seq=13604 Ack=298 Win=64313 Len=1460
ServerPort > ClientPort [ACK] Seq=15064 Ack=298 Win=64313 Len=1460


I assume the client here is asking for more data and the server is sending
two packets in response. Generally that pattern repeats over and over, but
suddenly at some point the client sends an ACK and there is no response for
20 seconds. After 20 seconds, the client resends the same ACK number, but
this time with the push flag set [PSH,ACK], and at this point the
conversation resumes.

Apparently my client packet is being lost somewhere, and the 20 seconds
represents a timeout on the client? Would the 20 second timeout likely be
a TCP timeout, or would it likely be an application timeout? Is there any
reason I should not adjust the timeout to say five seconds instead of 20?
If I want to change the Windows 2000 or Windows 2003 TCP timeout setting,
where do I do that?

On the server side of this, I'm surprised that the server would not be
sending out a request for more data if it is in the middle of an operation
that requires interaction. Is it normal behavior for a server to just let
the conversation hang and allow the client to timeout?

--
W



.



Relevant Pages

  • Re: Webservice problem (after iisreset)
    ... I was speaking about whatever means you're suing the make the call from the client. ... If it already waits one minute for the failure then it sounds like the timeout is already high enough. ... So use wsdl.exe to generate a .NET proxy to your webservice to see if that style of client has the same problems or not. ... If it does, then it sounds like something on the server, if it does not then it's likley your HTC framework. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: web serivce: client side timeout?
    ... client side but only from the server side. ... System.Net.Sockets.SocketException: A connection attempt failed ... asyncResult, Int32 timeout, Exception& exception) ... John Saunders | MVP - Windows Server System - Connected System ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Timeout value in new RDP 6.0 client
    ... I would suspect the problem is not so much the timeout as the severely overloaded server. ... Most likely you completed the first few stages of the connection, leading the client to believe everything was okay, but the server wasn't establishing the connection in the time you expected due to the load. ...
    (microsoft.public.windows.terminal_services)
  • Re: detecting the (brute) disconnection of a client
    ... crashed, and if an exception occurs, then the client is deconnected. ... You can either use the timeout itself as an indication of connection failure, or you can attempt to send data after the timeout. ... The server has no way to know if the connection has failed due to a client-side crash, or simply due to a temporary problem with the network. ... IMHO, it would be better to simply let the server continue to assume that the connection is valid unless there is some explicit, non-arbitrary verification that it's not. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: web serivce: client side timeout?
    ... client side but only from the server side. ... System.Net.Sockets.SocketException: A connection attempt failed ... asyncResult, Int32 timeout, Exception& exception) ... John Saunders | MVP - Windows Server System - Connected System ...
    (microsoft.public.dotnet.framework.webservices)

Quantcast