aynchronous web services connection end in Close_Wait state
From: tom (eeemwong_at_hotmail.com)
Date: 12/07/04
- Next message: James: "RE: is one language in .NET enough"
- Previous message: David Levine: "Re: How to automatically generate many publisher policies ?"
- Messages sorted by: [ date ] [ thread ]
Date: 7 Dec 2004 02:28:49 -0800
Hi all, I hope I can explain my problem clearly.
I have a .NET c# windows application calling a localhost web service
using
asynchronous callback.
While still waiting for the result, the user decides to end the
application,
my application then cast the applicable IAsyncResult to a
WebClientAsyncResult object and call the Abort() method of the latter
object.
Everything is fine, however, it left the server side with the
Close_Wait
connection state. (Under TCP term, it means the server still waiting
for the
ACK from the client). How can I make sure the .NET window application
will
send the ACK after calling the above Abort()?
I am using XP Pro, the IIS only allows max. 10 connections, the
Close_Wait
state connection will be kept opened for a very long time.
I have searched intensively but I can not find a solution. Hope someone
out
there can help!
Rgs
Tom
- Next message: James: "RE: is one language in .NET enough"
- Previous message: David Levine: "Re: How to automatically generate many publisher policies ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|