Re: The underlying connection was closed: An unexpected error occurred on a receive.

From: Dan Rogers (danro_at_microsoft.com)
Date: 12/20/04 

Date: Mon, 20 Dec 2004 21:52:17 GMT

Hi Vijay,
It might be an issue. I'm not sure what an empty WebProxy class does - I
suspect you have to set up the properties of that class for your
connections to succeed.

Regards,

Dan
--------------------
From: "Vijayakrishna Pondala" <pvijkris@hotmail.com>
References: <#d1saXm4EHA.924@TK2MSFTNGP14.phx.gbl>
<ANrRV3s4EHA.2732@cpmsftngxa10.phx.gbl>
Subject: Re: The underlying connection was closed: An unexpected error
occurred on a receive.
Date: Mon, 20 Dec 2004 12:08:19 +0530
Lines: 68
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <uB3#C6l5EHA.1264@TK2MSFTNGP12.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: lanner.hyd.deshaw.com 149.77.163.104
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:8198
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Hi Dan,

In our code, we are creating the WebService class, every time a method of
the class is called. In the constructor of the WebService class, we have
been setting the Proxy property to
GlobalProxySelection.GetEmptyWebProxy(). Is this code creating the problem
in any manner?

Thanks,

Vijaya Krishna P>

"Dan Rogers" <danro@microsoft.com> wrote in message
news:ANrRV3s4EHA.2732@cpmsftngxa10.phx.gbl...
> Hi Vijay,
>
> This is a known issue. Try (on the client side) turning off the proxy
> property that controls keep alives. Another option is to create/destroy
> the proxy between calls. The proxy is losing the underlying connection
> (HTTP can do that) and it doesn't retry when it has a connection already.
>
> I hope this helps
>
> Dan Rogers
> Microsoft Corporation
>
> --------------------
> From: "Vijayakrishna Pondala" <pvijkris@hotmail.com>
> Subject: The underlying connection was closed: An unexpected error
occurred
> on a receive.
> Date: Wed, 15 Dec 2004 10:50:52 +0530
> Lines: 16
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
> Message-ID: <#d1saXm4EHA.924@TK2MSFTNGP14.phx.gbl>
> Newsgroups: microsoft.public.dotnet.framework.webservices
> NNTP-Posting-Host: lanner.hyd.deshaw.com 149.77.163.104
> Path:
>
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14
> phx.gbl
> Xref: cpmsftngxa10.phx.gbl
> microsoft.public.dotnet.framework.webservices:8104
> X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
>
> Hi,
>
> We are using the following error randomly, when accessing a webservice
> method/servlet hosted on JBoss application server:
>
> The underlying connection was closed: An unexpected error occurred on a
> receive.
>
> We are using .NET v1.1.
>
> Does anyone have idea about the reason/solution for this exception?
>
> Thanks,
> Vijaya Krishna P.
>
>
>

Relevant Pages

  • Re: The underlying connection was closed: An unexpected error occurred on a receive.
    ... In the constructor of the WebService class, ... Vijaya Krishna P> ... Try turning off the proxy ... The proxy is losing the underlying connection ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Upload a file from a Pocket PC to a web server?
    ... I do have Write option checked off in IIS on the virtual drectory. ... "The underlying connection was closed: An unexpected error occurred on a ... >>> Alex Feinman ...
    (microsoft.public.pocketpc.developer)
  • RE: The underlying connection was closed: An unexpected error occurred on a receive.
    ... Try turning off the proxy ... property that controls keep alives. ... Another option is to create/destroy ... Subject: The underlying connection was closed: An unexpected error occurred ...
    (microsoft.public.dotnet.framework.webservices)
  • IIS Timeout
    ... The underlying connection was closed: An unexpected error occurred on a ... Increasing the httpRuntime executionTimeout in the web.config to 3600 ... setting for all applications running on the same computer. ...
    (microsoft.public.dotnet.framework.remoting)
  • RE: Underlying connection was closed
    ... The underlying connection was closed. ... An unexpected error ... could not be resolved, verify correct proxy configuration. ... Would this not happen when the webservices client is ...
    (microsoft.public.dotnet.framework.webservices)