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" <pv******@hotmail.com>
References: <#d*************@TK2MSFTNGP14.phx.gbl>
<AN**************@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: <uB**************@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!TK2MSFT NGP08.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" <da***@microsoft.com> wrote in message
news:AN**************@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" <pv******@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: <#d*************@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!TK2MSFT NGP08.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.