i am currently challenging a problem that suddenly started to happen in my production environment when invoking a WS method from a windows-service .NET app.
The windows service is waiting for requests incoming through MQ, unwraps these requests from an "MQ XML packet" and redirects these requests to the web service. This web service has only one web method, which is kind of "main entry point" for the
underlying backend application.
This monday approx. 30% of attempts to invoke that web method are failing with message: The underlying connection was closed: Unable to connect to the remote server.
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object?! parameters)
at MyWebService.GetResponse(String requestMessage, String& responseMessage)
View Complete Post