S
Steve Piccolo
We’ve been seeing intermittent .NET “underlying connection was closedâ€
exceptions thrown while trying to invoke a Web service from ASP.NET. We are
running .NET 1.1, IIS 6, and Win2003.
This error is occurring where a client invokes a Web service on a front-end
server that in turn invokes a Web service on a middle-tier server. It fails
on the call to the middle-tier server. The error appears to happen when the
client has been sitting idle for approximately 6 minutes and then invokes the
Web service. After the failure, it works fine for subsequent invocations.
We found the following article that addresses this problem:
http://support.microsoft.com/kb/819450. We understand this fix is rolled up
in .NET 1.1 SP1; we've applied that but the errors have continued. The
article also suggests disabling Keep-Alives; however, we can't do that
because Keep-Alives are required for Integration Windows Authentication,
which we are using where the error is occurring.
Here is a typical stack trace for this error:
System.Net.WebException: The underlying connection was closed: An unexpected
error occurred on a receive. at
System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest
request) at
System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest
request) at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Ebusiness.Pem.FileTransfer.ExternalServices.ExternalMiddleTierWS.DownloadNextFile()
at
Ebusiness.Pem.FileTransfer.ExternalServices.ExternalWebService.DownloadNextFile()
Any help would be greatly appreciated!
exceptions thrown while trying to invoke a Web service from ASP.NET. We are
running .NET 1.1, IIS 6, and Win2003.
This error is occurring where a client invokes a Web service on a front-end
server that in turn invokes a Web service on a middle-tier server. It fails
on the call to the middle-tier server. The error appears to happen when the
client has been sitting idle for approximately 6 minutes and then invokes the
Web service. After the failure, it works fine for subsequent invocations.
We found the following article that addresses this problem:
http://support.microsoft.com/kb/819450. We understand this fix is rolled up
in .NET 1.1 SP1; we've applied that but the errors have continued. The
article also suggests disabling Keep-Alives; however, we can't do that
because Keep-Alives are required for Integration Windows Authentication,
which we are using where the error is occurring.
Here is a typical stack trace for this error:
System.Net.WebException: The underlying connection was closed: An unexpected
error occurred on a receive. at
System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest
request) at
System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest
request) at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Ebusiness.Pem.FileTransfer.ExternalServices.ExternalMiddleTierWS.DownloadNextFile()
at
Ebusiness.Pem.FileTransfer.ExternalServices.ExternalWebService.DownloadNextFile()
Any help would be greatly appreciated!