Request timed out error only when running release mode not debug

[TimG]

I have a web service that performs a long running task (typically 10-20
minutes) via an async call. When I run the web service either within the
debugger or with Debug=True it works as expected. When I run it with
Debug=False it gets a HttpException, Request timed out after 5 minutes.

I have tried upping the timeout to 15 minutes (even though MSDN docs say
timeout is for synchronous calls) and the error still happens after 5 minutes.

Any thoughts or hints on what is happening.

 

[John Saunders [MVP]]

I have a web service that performs a long running task (typically 10-20
minutes) via an async call. When I run the web service either within the
debugger or with Debug=True it works as expected. When I run it with
Debug=False it gets a HttpException, Request timed out after 5 minutes.

I have tried upping the timeout to 15 minutes (even though MSDN docs say
timeout is for synchronous calls) and the error still happens after 5
minutes.

Any thoughts or hints on what is happening.

Which request timed out? A request from a client application? If so, has the
client changed, or is it only the server that has changed, from debug to
non-debug modes?

 

[TimG]

I don't have the stack trace right now so this is from memory. The timeout
was propagated as a soapexception to the client in something like
GetAsyncResponse (client should be waiting for the server to finish the async
method). The server was not running in either debug mode or within a
debugger, the client was running within the visual studio debugger. There
was no stack trace information supplied with the soapexception, only "Request
timed out".
--
Thanks,

Tim

 

[Steven Cheng[MSFT]]

Hi Tim,

For ASP.NET webservice, when you call it from .net client(through
autogenerated proxy class) and the service method have long-run task to
run, you may get timeout error due to the following two causes:

** The ASP.NET runtime has a "executionTime" limitation, by default it is
set to 110 seconds. And this timeout only take effect when running in
release mode.

#httpRuntime Element (ASP.NET Settings Schema)
http://msdn2.microsoft.com/en-us/library/e1f13641.aspx


** The .NET webservcie's client proxy class (derived from WebClient

#WebClientProtocol.Timeout Property
http://msdn2.microsoft.com/en-us/library/system.web.services.protocols.webcl
ientprotocol.timeout(VS.71).aspx

For your scenario, the error message is more likely due to the server-side
"executionTimeout" setting. You can try enlarge the "executionTimeout"
attribute in the <httpRuntime> element in web.config file to see whether it
helps.

If you have anything unclear, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



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

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.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.



--------------------

From: =?Utf-8?B?VGltRw==?= <[email protected]>
References: <[email protected]>

Subject: Re: Request timed out error only when running release mode not deb
Date: Mon, 27 Aug 2007 19:50:01 -0700

I don't have the stack trace right now so this is from memory. The timeout
was propagated as a soapexception to the client in something like
GetAsyncResponse (client should be waiting for the server to finish the async
method). The server was not running in either debug mode or within a
debugger, the client was running within the visual studio debugger. There
was no stack trace information supplied with the soapexception, only "Request
timed out".
--
Thanks,

Tim

 

[TimG]

Thanks, updating ExecutionTimeout solved my problem.

One more question, is there a way to set this within code so that the
timeout can be very long (up to a day) for a specific call?

--
Thanks,

Tim

Hi Tim,

For ASP.NET webservice, when you call it from .net client(through
autogenerated proxy class) and the service method have long-run task to
run, you may get timeout error due to the following two causes:

** The ASP.NET runtime has a "executionTime" limitation, by default it is
set to 110 seconds. And this timeout only take effect when running in
release mode.

#httpRuntime Element (ASP.NET Settings Schema)
http://msdn2.microsoft.com/en-us/library/e1f13641.aspx


** The .NET webservcie's client proxy class (derived from WebClient

#WebClientProtocol.Timeout Property
http://msdn2.microsoft.com/en-us/library/system.web.services.protocols.webcl
ientprotocol.timeout(VS.71).aspx

For your scenario, the error message is more likely due to the server-side
"executionTimeout" setting. You can try enlarge the "executionTimeout"
attribute in the <httpRuntime> element in web.config file to see whether it
helps.

If you have anything unclear, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



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

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.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.



--------------------

From: =?Utf-8?B?VGltRw==?= <[email protected]>
References: <[email protected]>

 

[Steven Cheng[MSFT]]

Thanks for your reply Tim,

For the <httpRuntime> setting, I'm afraid it must be configured statically
and do not allow runtime/programmatically configuring. However, ASP.NET
web application support a hierarchial configuration model so that you can
specify customized and particular settings(those setting allow configured
in sub directories) for a sub directory(or asmx, aspx page). You can have
a look at the following reference:

#location Element (ASP.NET Settings Schema)
http://msdn2.microsoft.com/en-us/library/b6x6shw7.aspx

#How to: Configure Specific Directories Using Location Settings
http://msdn2.microsoft.com/en-us/library/ms178692(VS.80).aspx

thus, for your scenario, if possible, you can gather all those webmethods
that will need long-run execution into a single webservice(asmx endpoint)
and put it in a particular sub folder and specify a larege
"executionTimeout" setting for that particular sub dir. How do you think?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


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

 

[Steven Cheng[MSFT]]

Hi Tim,

Any further question on this? If so, please feel free to let me know.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


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


--------------------