Luke,
Are you currently overriding 'GetWebRequest()' in the proxy class on the
client and setting keep alives to false?
Alex
> Hi,
>
[quoted text clipped - 20 lines]
> Many Thanks,
> Luke Venediger.
lukev123@gmail.com - 15 Oct 2004 16:15 GMT
Hi Alex,
We're not overriding GetWebRequest in the proxy. As for the keep-alives
they are enabled on the web server. Should they be disabled?
Thanks,
Luke Venediger.
Warren Reinke - 25 Oct 2004 13:30 GMT
We're doing the same thing. Client application using web services on
the 1.1 .NET Framework. Our servers are Windows 2003 Web Edition.
Every now and then we're receiving the "The underlying connection was
closed: Could not establish secure channel for SSL/TLS." error.
Has anyone else responded with reasons for this error?
Thanks
fredplain@hotmail.com - 26 Oct 2004 08:44 GMT
Hello ,
I have exactly the same problem : using TCPListener and socket on two machine (one client, one server).
On two XPs, that works.
On two 2003 Servers, after a while I get the same message : 'Unable to read data from the transport connection ..'
Isn' t it against some 2003 timeouts ??
If you find some topics to help me solving the problem , please let me know (I will let you know when I' ll fix)
Thanks
Fred
fredplain@hotmail.com
lukev123@gmail.com - 27 Oct 2004 08:49 GMT
Hi All,
It sounds like everyone here is using load balanced servers. Apparently
the problem happens when you use a proxy server for
incoming and outgoing traffic (as might be the case in a load-balanced
environment.) A solution is to specify the proxy address in the
machine.config file of your web servers.
For example:
<proxy usesystemdefault="false"
proxyaddress="http://yourproxy"
bypassonlocal="true" />
There is a Microsoft knowledge base article on configuring a bypass
proxy on your machine:
http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;307220
Hope that helps,
Cheers,
lukev123@gmail.com - 27 Oct 2004 08:49 GMT
Hi All,
It sounds like everyone here is using load balanced servers. Apparently
the problem happens when you use a proxy server for
incoming and outgoing traffic (as might be the case in a load-balanced
environment.) A solution is to specify the proxy address in the
machine.config file of your web servers.
For example:
<proxy usesystemdefault="false"
proxyaddress="http://yourproxy"
bypassonlocal="true" />
There is a Microsoft knowledge base article on configuring a bypass
proxy on your machine:
http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;307220
Hope that helps,
Cheers,
Luke.
Hi,
To get rid of this problem, a work around that is effective is to disable
keep-alives in the generated .NET proxy client. What is happening is that
the reused connection gets closed, but the proxy isn't accounting for this
so it tries to use a dead connection. The work around is to prevent the
proxy from making a request with keep-alives enabled.
Regards
Dan Rogers
Microsoft Corporation
--------------------
>From: lukev123@gmail.com (Luke Venediger)
>Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
[quoted text clipped - 7 lines]
>Content-Transfer-Encoding: 8bit
>X-Trace: posting.google.com 1097498090 8848 127.0.0.1 (11 Oct 2004
12:34:50 GMT)
>X-Complaints-To: groups-abuse@google.com
>NNTP-Posting-Date: Mon, 11 Oct 2004 12:34:50 +0000 (UTC)
>Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!news-out.cwix.com!newsfeed.cwix.co
m!border1.nntp.dca.giganews.com!nntp.giganews.com!news.glorb.com!postnews1.g
oogle.com!not-for-mail
>Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:25816
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 22 lines]
>Many Thanks,
>Luke Venediger.