Re: The underlying connection was closed
- From: "kirk" <nokirkspam@xxxxxxxxxxxxxxxxx>
- Date: Tue, 17 Apr 2007 12:19:12 -0600
John,
1) The solutions I was finding on the web were all based on the 1.1 and 1.0
framework. They involved tweaking the resource.cs file by overriding the
WebRequest method and setting the KeepAlive = false. Basicly, force the
creation of a new connection for every request. I guess that MS had a
support item on it at
'http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b819450' but
they have since removed the topic.
I can't follow the recommend because in VS 2005, there is no resource.cs
file any more. this file is generated on the fly by the .net framework
after deployment.
2) the web service is configured for ssl using a purchased certificate.
When my client hits my ws using https, my call to the 3rd party ws fails
with the error stated. If I allow my client to hit my ws without ssl, my
call to the 3rd party ws works just fine. In both cases I am hitting the
3rd party ws using ssl.
Kirk
"John Saunders [MVP]" <john.saunders at trizetto.com> wrote in message
news:uJOhQeRgHHA.4260@xxxxxxxxxxxxxxxxxxxxxxx
"kirk" <nokirkspam@xxxxxxxxxxxxxxxxx> wrote in message
news:uip$7TQgHHA.4916@xxxxxxxxxxxxxxxxxxxxxxx
Environment:
c#, Framwork 2.0, Win2003 server, IIS 6.0, Copy deployment (uncompiled
source code deployed to server)
I have written a web service that calls another web service. The ws I am
calling is third party, but written in .net (unknown framework version).
I am calling the 3rd party ws over https.
When my ws is called without ssl everything works great. However, when
my client is calling my ws using https, I get the following error:
The underlying connection was closed: An unexpected error occurred on a
receive.
System.Net.WebResponse GetWebResponse(System.Net.WebRequest)
...
I won't post the entire stack trace for size reasons.
The error will only pop up after a number of days of everything working
just fine. No changes on the server or the source code.
I have seen a number of 'solutions' to this problem, but they all apply
to 1.0 and 1.1 frameworks.
What did those solutions say was the cause of the problem?
Does anyone know why this is happening and what I can do about it in 2.0?
I don't know for sure what's happening, but does your web server have SSL
configured?
--
John Saunders [MVP]
.
- Follow-Ups:
- Re: The underlying connection was closed
- From: John Saunders [MVP]
- Re: The underlying connection was closed
- References:
- The underlying connection was closed
- From: kirk
- Re: The underlying connection was closed
- From: John Saunders [MVP]
- The underlying connection was closed
- Prev by Date: Re: The underlying connection was closed
- Next by Date: Re: The underlying connection was closed
- Previous by thread: Re: The underlying connection was closed
- Next by thread: Re: The underlying connection was closed
- Index(es):
Relevant Pages
|