I have a client that consumes a WebService using a WSE 2.0 sp3 interface. I
use a WebProxy as generated by VS.Net, based on a webService URL.
Occasionaly when debugging I get an unhandled expection in disassembly code:
"Connection was forcidbly closed by remote host"
stack trace:
system.dll!System.Net.Sockets.Socket.EndReceive(Sy stem.IAsyncResult asyncResult = {System.Net.Sockets.OverlappedAsyncResult}) + 0x204 bytes
system.dll!System.Net.Sockets.NetworkStream.EndRea d(System.IAsyncResult
asyncResult = {System.Net.Sockets.OverlappedAsyncResult}) + 0xf4 bytes
system.dll!System.Net.Connection.ReadCallback(Syst em.IAsyncResult
asyncResult = {System.Net.Sockets.OverlappedAsyncResult}) + 0xbf bytes
system.dll!System.Net.LazyAsyncResult.InvokeCallba ck() + 0x27 bytes
system.dll!System.Net.LazyAsyncResult.InvokeCallba ck(bool
completedSynchronously = false, System.Object result = {0}) + 0x23 bytes
system.dll!System.Net.Sockets.OverlappedAsyncResul t.CompletionPortCallback(uint
errorCode = 10054, uint numBytes = 0, System.Threading.NativeOverlapped*
nativeOverlapped = 2063624) + 0xf2 bytes
Most of the time this exception is handled by the .Net Runtime but sometimes
it results in a time-out on the WebService SOAP-call I posted to the
WebService.
How can I prevent this from happening?
Thanks,
--
rvangeldrop