Rob,
Thanks for the reply.
There is one more interesting thing happened during the connection closed
scenario, the web servicce actually DID the work , even though from the
client side, it report a WebException, I guess it is because the
communication is severed, that's why I said retry did not work well. Just
FYI.
I agree with you , after googled two days, my final decision is do nothing,
there is no way to prevent this kind of scenario from happening, in our
production environment, it allows retry, as long as conneciton closed is not
happening too frequently,we are fine. Also, I tend to give the challenge to
our system engineer group to resolve the mystry of who close the connection.
For application, we have done the max we can.
Mike
> Mike,
>
[quoted text clipped - 36 lines]
>> >
>> > Any ideas? Have I missed something?
Joel Zhou - 28 Sep 2004 14:16 GMT
I have a similar issue, the error is on "An unexpected error occurred
on a receive" rathan than "sent". I was able to workaround the problem
by increasing the "Connection timeout" (IIS Manager -> Web Site ->
Properities).
The error also happens with both sync and async call, and it only
happens on Win2003 with IIS 6.0 (not on WinXP with .Net 1.1). You can
see more detail in link I posted below. I posted a question yesterday
and hopefully I will get some reply.
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=3bdcbe2f.0409271329.3
cfd48cc%40posting.google.com&rnum=1&prev=/groups%3Fq%3D%2522The%2520underlying%2
520connection%2520was%2520closed%2522%2520joel%2520zhou%26hl%3Den%26lr%3D%26ie%3
DUTF-8%26sa%3DN%26tab%3Dwg