[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.aspnet.webservices

Server becomes unavailable

Erik

1/14/2003 7:40:00 AM

I have a couple of web services that take a very long time to execute due to
big queries. When I test them out, after about 3 minutes I get the "Server
Unavailable" red letters and my event log says the web service has timed
out.

This occurs even after I bump the command timeout for Sql Server to 0
(indefinetly), so I don't think it's Sql. I'm testing this through the
Default test page, not consuming as a webservice, so I don't think it's a
client setting.

Is there a way to adjust the web service timeout on the server?
3 Answers

Pierre Greborio

1/14/2003 9:38:00 AM

0

You can increase the timeout attribute to httpRuntime of the web.config.
Ref.: ms-help://MS.NETFrameworkSDK/cpgenref/html/gngrfhttpruntimesection.htm

Pierre

--
-----------------------------------------------------------
Pierre Greborio
http://www.ugi...
-----------------------------------------------------------
"Erik" <eolson@callabacus.com> wrote in message
news:Ow#W9d5uCHA.2632@TK2MSFTNGP09...
> I have a couple of web services that take a very long time to execute due
to
> big queries. When I test them out, after about 3 minutes I get the
"Server
> Unavailable" red letters and my event log says the web service has timed
> out.
>
> This occurs even after I bump the command timeout for Sql Server to 0
> (indefinetly), so I don't think it's Sql. I'm testing this through the
> Default test page, not consuming as a webservice, so I don't think it's a
> client setting.
>
> Is there a way to adjust the web service timeout on the server?
>
>

(garygumsft)

1/14/2003 10:33:00 AM

0

Hi Erik,

Please have a look at the executionTimeout attribute of the <httpRuntime>
section in the machine.config or the corresponding web.config file.

executionTimeout is the maximum time an .aspx page can run before timing
out. The default is 90 seconds, but you should extend this value for pages
that perform long database queries or remote calls to a Web service. This
attribute corresponds to the Server.ScriptTimeout property.

In addition, there is an article on how to deal with Large Data situation:

Large Data Strategies
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/d...
tml/service11072001.asp

Gary

This posting is provided "AS IS", with no warranties, and confers no
rights. Enjoyed ASP.NET? http://w...

(Wade Mascia [MS])

1/15/2003 5:43:00 PM

0

Just want to point out the executionTimeout/Server.ScriptTimeout will not
result in the error that Erik describes. This error message comes when the
worker process has died. In the case of a simple script timeout, only the
thread is terminated (via ThreadAbortException) and the user won't see the
"Server Unavailable" error.

Notice in this case that the event log tells you the worker process is
being recycled for suspected deadlock. The relevant setting is
responseDeadlockInterval. Keep in mind that once you increase this setting
to avoid the "Server Unavailable" error, you'll *also* need to change the
executionTimeout/Server.ScriptTimeout to avoid that error.

HTH

~Wade Mascia, MCSD
Developer Support Engineer - WebServices, EnterpriseServices, MTS,
COM+, ASP/COM
 Microsoft Corporation

And now, a word from our lawyers: "This posting is provided 'AS IS' with
no warranties, and confers no rights."
--------------------
| X-Tomcat-ID: 196563609
| References: <Ow#W9d5uCHA.2632@TK2MSFTNGP09>
<eSnc7j6uCHA.1624@TK2MSFTNGP11>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: garygu@online.microsoft.com (garygumsft)
| Organization: Microsoft
| Date: Tue, 14 Jan 2003 09:33:34 GMT
| Subject: Re: Server becomes unavailable
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
| Message-ID: <6pfk#$6uCHA.2072@cpmsftngxa06>
| Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
| Lines: 20
| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
| Path: cpmsftngxa09!cpmsftngxa10!cpmsftngxa06
| Xref: cpmsftngxa09
microsoft.public.dotnet.framework.aspnet.webservices:14822
|
| Hi Erik,
|
| Please have a look at the executionTimeout attribute of the
<httpRuntime>
| section in the machine.config or the corresponding web.config file.
|
| executionTimeout is the maximum time an .aspx page can run before timing
| out. The default is 90 seconds, but you should extend this value for
pages
| that perform long database queries or remote calls to a Web service.
This
| attribute corresponds to the Server.ScriptTimeout property.
|
| In addition, there is an article on how to deal with Large Data
situation:
|
| Large Data Strategies
|
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/d...
| tml/service11072001.asp
|
| Gary
|
| This posting is provided "AS IS", with no warranties, and confers no
| rights. Enjoyed ASP.NET? http://w...
|
|