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

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Vijayakrishna Pondala (pvijkris_at_hotmail.com)
Date: 12/20/04

  • Next message: jb: "Re: Namespace prefix change" 
    Date: Mon, 20 Dec 2004 12:08:19 +0530

    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.
    >
    >
    >

  • Next message: jb: "Re: Namespace prefix change"

    Relevant Pages

    • Re: The underlying connection was closed: An unexpected error occurred on a receive.
      ... Subject: The underlying connection was closed: An unexpected error ... In the constructor of the WebService class, ... Try turning off the proxy ...
      (microsoft.public.dotnet.framework.webservices)
    • 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)
    • Re: Programmatically add Proxy to web request
      ... I know that the WebService class has a Proxy property. ... I am trying to ensure that every request to the web application ... This makes the service proxy direct its ...
      (microsoft.public.dotnet.framework.webservices)
    • Need help for dotNet
      ... I write a C# to get information from a XML site, when I run my program at ... But when in office (no proxy, no firewall, port 80 is open), I've got this ... Unhandled Exception: System.Net.WebException: The underlying connection was ... at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) ...
      (microsoft.public.dotnet.framework)
    • Need help for dotNet
      ... I write a C# to get information from a XML site, when I run my program at ... But when in office (no proxy, no firewall, port 80 is open), I've got this ... Unhandled Exception: System.Net.WebException: The underlying connection was ... at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) ...
      (microsoft.public.dotnet.framework.aspnet)