underlying connection has closed

I am consuming continously my own web-services on a localhost client with a
rate of perhaps 35 request/response-pairs a minute.
I am using "invoke-id=1", so there is at the same time only one request
pending.
After a runtime of 4 days I get the system.net.exception "The underlying
connection was closed: An unexpected error occured on a send"
Subsequent ws-calls in this state result also in the same exception,
browsing a local hosted html-file results in HTTP-error 504.
After a restart of windows all goes well (for the next 4 days).
I read some knowledgebase articles (826210,...) about this behaviour and
tried the webRequest-properties KeppAlive=false and
ProtocolVersion = HttpVersion.Version10 - but no success.
client, server = Win2003server, sp2; Net 2.0

It's a simple HTTP-Web_service, I don't use HTTPS and WSE, the IIS-settings
are the default.

What is the reason for this problem/bug?
What's a stable solution with no performance drawback for a production
environment?
When does MS solve this bug finally?

--
best regards
friedhelm

RE: underlying connection has closed

Hi Friedhelm,

This looks mainly an ASP.net web service stability issue and our ASP.net
engineer has followed up you in ASP.net newsgroup. Please work with him on
the troubleshooting and I will keep an eye on your thread to see if there
is anything I can help on IIS side.

Meanwhile, since the web service can work properly for about 4 days, I'd
like to suggest you adjust some IIS web server health related
configurations to see if this will help.

In IIS manager, you can first create a dedciated application pool for the
web service. This will ensure the WS always be run in an isolated worker
process and then it will not affect/be affected with other web applications.

Second, open the web service's application pool property, you can configure
IIS to recycle the web service's worker process in certain time, for
example: midnight. The setting is sometimes helpful for problems caused by
potential memory leak, etc.

Thanks.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx .

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

RE: underlying connection has closed

Thank you,
but what's my job now?
Should I wait for an eMail from your ASP.net
engineer?
--
best regards
friedhelm


""WenJun Zhang[msft]"" wrote:

> Hi Friedhelm,
>
> This looks mainly an ASP.net web service stability issue and our ASP.net
> engineer has followed up you in ASP.net newsgroup. Please work with him on
> the troubleshooting and I will keep an eye on your thread to see if there
> is anything I can help on IIS side.
>
> Meanwhile, since the web service can work properly for about 4 days, I'd
> like to suggest you adjust some IIS web server health related
> configurations to see if this will help.
>
> In IIS manager, you can first create a dedciated application pool for the
> web service. This will ensure the WS always be run in an isolated worker
> process and then it will not affect/be affected with other web applications.
>
> Second, open the web service's application pool property, you can configure
> IIS to recycle the web service's worker process in certain time, for
> example: midnight. The setting is sometimes helpful for problems caused by
> potential memory leak, etc.
>
> Thanks.
>
> Sincerely,
>
> WenJun Zhang
>
> Microsoft Online Community Support
>
> ==================================================
>
> Get notification to my posts through email? Please refer to:
> http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at:
>
> http://msdn.microsoft.com/subscriptions/support/default.aspx .
>
> ==================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

RE: underlying connection has closed

Hi Friedhelm

Have you seen my colleague Steven's follow up in:
microsoft.public.dotnet.framework.webservices ?

Thanks.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx .

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.