D
Dmitriy
I am having a thread blocking issue of some sort when invoking a SoapHttpClientProtocol object after having a System.Net.WebException{"The request failed with HTTP status 502: Connection refused." } thrown during the previous invocation of a different (or the same one - it doen't matter) instance of SoapHttpClientProtocol. Exceptions coming from the target service do not cause blockage - only happens after connection was refused (the target service was down).
Anybody have seen anything like this?
Here is the relevant part of the stack :
mscorlib.dll!System.Threading.WaitHandle::WaitOne(__int32 millisecondsTimeout = 100000, bool exitContext = false) + 0x78 bytes
system.dll!System.Net.HttpWebRequest::GetRequestStream() + 0x77 bytes
system.web.services.dll!System.Web.Services.Protocols.SoapHttpClientProtocol::Invoke(String* methodName = "test", System.Object[] parameters = {Length=5}) + 0xa8 bytes
Anybody have seen anything like this?
Here is the relevant part of the stack :
mscorlib.dll!System.Threading.WaitHandle::WaitOne(__int32 millisecondsTimeout = 100000, bool exitContext = false) + 0x78 bytes
system.dll!System.Net.HttpWebRequest::GetRequestStream() + 0x77 bytes
system.web.services.dll!System.Web.Services.Protocols.SoapHttpClientProtocol::Invoke(String* methodName = "test", System.Object[] parameters = {Length=5}) + 0xa8 bytes