468,161 Members | 1,964 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,161 developers. It's quick & easy.

aynchronous web services connection end in Close_Wait state

tom
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

Nov 23 '05 #1
1 4666
Hi tom.

This is not a perfect solution.
Do you know WS-Eventing? WS-Eventing is asynchronous Web Service spec.
Anyway,
First You can set IIS Time-out options.
Web Service have a dicection. so General Web Service use by-direction. (Call
and Receive result). If you see the WSDL Spec, you can get informaiton of Web
Service direction options.

"tom" wrote:
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

Nov 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by dabuskol | last post: by
reply views Thread by Holger Steinestel | last post: by
18 posts views Thread by Larry Herbinaux | last post: by
7 posts views Thread by C Jay Pemberton Jr | last post: by
reply views Thread by krishnaraju | last post: by
reply views Thread by gcreed | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.