Re: long delay after invoking web service until SOAP message is sent

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"beachdog" <dhorton@xxxxxxxxxxxx> wrote in message
news:1177125433.642314.17480@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have built a web service consumer application by adding a web
reference for a vendor-provided wsdl file. My client is
interoperating with the server just fine, in terms of sending a
request and receiving and properly parsing a response, but the problem
is that when I step through it in the debugger (or even when I run the
executable) there is a delay of about 15 seconds after executing my
XXXAsync method to invoke the web service until the SOAP request
message is actually sent out over the wire. I have no idea what the
program is doing during this time. Anyone have an idea of what might
be causing the delay? It almost seems like the web consumer is trying
to resolve some dns names or something, but I have set the url to send
to to be a specific ip address so there is no need for dns there. My
client PC is also connecting to the server over a VPN, not sure if
that plays into this somehow.

I have taken an ethereal trace during this time to see what is going
over the network during this 15 second delay, and what I see is a
bunch of SMB messages that Ethereal decodes as Trans2 requests and
responses, followed 12 seconds later by some Netbios name queries,
followed at about the 15 second interval by the SOAP message.


To whom are these SMB messages directed? What resource are they about? That
may give you a clue as to what's going on.

This isn't standard web services behavior, so it's likely to be something
specific to your environment; perhaps something to do with anti-virus
software, or some other piece of code that thinks it's a good idea to delay
you for 15 seconds while you're in the debugger.
--

John Saunders [MVP]


.

Relevant Pages

  • Re: HttpWebRequest taking lot longer compared to ServerXMLHTTP
    ... the backend server is challenging the request for credentials. ... server is requesting Windows Integrated Authentication, ... and that will contribute to the delay. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Socket.BeginReceive does not handle incoming data immediately
    ... Thanks for the reply.>Does the server send the same three responses for the second user? ... I was referring to the 3 responses for the first request. ... is always ~200 millisecs delay. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Error number: 0x801901F7
    ... This is a temporary HTTP 503 error and should be ok after a delay. ... "The server is currently unable to handle the request due to a temporary ...
    (microsoft.public.windowsupdate)
  • Re: Socket.BeginReceive does not handle incoming data immediately
    ... the formats of these 3 responses are the same. ... I was referring to the 3 responses for the first request. ... Since the server scales great and responds immediately (it has been ... Even if there was some delay due to the i/o thread waiting to ...
    (microsoft.public.dotnet.languages.csharp)
  • [REVS] NTLM HTTP Authentication is Insecure By Design
    ... in front of a web server, and that proxy server shares a single TCP ... These are attacks that make use of non-RFC HTTP requests (HTTP Request ... the authentication is associated with the ...
    (Securiteam)