| Groups | Blog | Home |
asp.net : How to extend running time for Web Application?
I write a Web Application: its UI has a DataGrid controller. The web application gets huge data from SQL Server, then shows the result after processing these data. It needs much time to run it. But, it happened an error after running less than 60 seconds. This error didn't explain detail. I set Server.ScriptTimeout=600; <httpRuntime executionTimeout="600" /> cmd.CommandTimeout=600; But, it doesn't work. It still has an error in 60 seconds. How to solve it? Thanks.
I don't configure the IIS setting.
I already set ScriptTimeout and SqlCommand's CommandTimeout, but it doesn't work. The Web Page only needs a DataGrid which shows the processing result. So, I use Response.BufferOutput=false; , it still doesn't work. ASP Web Page can use Server.ScriptTimeout to extend running time, but ASP.NET seems no work for it. I think ASP.NET should have this function, but I don't find it until now. If you have other suggestions, please kindly tell me. Thanks. [quoted text, click to view] "Yunus Emre ALPÖZEN" wrote:
> May your application have 60 seconds time out. which configured via IIS > manager. My advice you to test it using Response.BufferOutput is false. and > flush it at some count of records. > > Also, i wonder if does it give a sql connection time out or ASP.NET timeout? > If it gives a sql connection time out, you must set timeout in your > connection string... > > -- > Thanks, > Yunus Emre ALPÖZEN > > > > "Grace" <Grace@discussions.microsoft.com> wrote in message > news:9E4CA84B-5015-4B30-9D99-3C8FE6B27DB3@microsoft.com... > > Hello, > > I write a Web Application: > > its UI has a DataGrid controller. > > The web application gets huge data from SQL Server, > > then shows the result after processing these data. > > > > It needs much time to run it. > > But, it happened an error after running less than 60 seconds. > > This error didn't explain detail. > > I set > > Server.ScriptTimeout=600; > > <httpRuntime executionTimeout="600" /> > > cmd.CommandTimeout=600; > > But, it doesn't work. > > It still has an error in 60 seconds. > > > > How to solve it? > > Thanks. > > > >
Just a thought, but from my experience, any query result that takes more
than 60 seconds to return might be way too big to send to a web page. How much data are you returning? Could you reduce the time to return the data by tuning and optimizing your query? Do you have the appropriate indexes, etc? DalePres MCAD, MCDBA, MCSE [quoted text, click to view] "Grace" <Grace@discussions.microsoft.com> wrote in message news:9E4CA84B-5015-4B30-9D99-3C8FE6B27DB3@microsoft.com... > Hello, > I write a Web Application: > its UI has a DataGrid controller. > The web application gets huge data from SQL Server, > then shows the result after processing these data. > > It needs much time to run it. > But, it happened an error after running less than 60 seconds. > This error didn't explain detail. > I set > Server.ScriptTimeout=600; > <httpRuntime executionTimeout="600" /> > cmd.CommandTimeout=600; > But, it doesn't work. > It still has an error in 60 seconds. > > How to solve it? > Thanks. >
May your application have 60 seconds time out. which configured via IIS
manager. My advice you to test it using Response.BufferOutput is false. and flush it at some count of records. Also, i wonder if does it give a sql connection time out or ASP.NET timeout? If it gives a sql connection time out, you must set timeout in your connection string... -- Thanks, Yunus Emre ALPÖZEN [quoted text, click to view] "Grace" <Grace@discussions.microsoft.com> wrote in message news:9E4CA84B-5015-4B30-9D99-3C8FE6B27DB3@microsoft.com... > Hello, > I write a Web Application: > its UI has a DataGrid controller. > The web application gets huge data from SQL Server, > then shows the result after processing these data. > > It needs much time to run it. > But, it happened an error after running less than 60 seconds. > This error didn't explain detail. > I set > Server.ScriptTimeout=600; > <httpRuntime executionTimeout="600" /> > cmd.CommandTimeout=600; > But, it doesn't work. > It still has an error in 60 seconds. > > How to solve it? > Thanks. >
Does your exception is thrown by SQL server or ASP.NET? Also if you set your
connection string timeout may your connection expire... -- Thanks, Yunus Emre ALPÖZEN [quoted text, click to view] "Grace" <Grace@discussions.microsoft.com> wrote in message news:F5CD35B6-A976-4F07-8E19-5FB14915F646@microsoft.com... >I don't configure the IIS setting. > I already set ScriptTimeout and SqlCommand's CommandTimeout, but it > doesn't > work. > The Web Page only needs a DataGrid which shows the processing result. > So, I use Response.BufferOutput=false; , it still doesn't work. > > ASP Web Page can use Server.ScriptTimeout to extend running time, > but ASP.NET seems no work for it. > > I think ASP.NET should have this function, but I don't find it until now. > > If you have other suggestions, please kindly tell me. > Thanks. > > > "Yunus Emre ALPÖZEN" wrote: > >> May your application have 60 seconds time out. which configured via IIS >> manager. My advice you to test it using Response.BufferOutput is false. >> and >> flush it at some count of records. >> >> Also, i wonder if does it give a sql connection time out or ASP.NET >> timeout? >> If it gives a sql connection time out, you must set timeout in your >> connection string... >> >> -- >> Thanks, >> Yunus Emre ALPÖZEN >> >> >> >> "Grace" <Grace@discussions.microsoft.com> wrote in message >> news:9E4CA84B-5015-4B30-9D99-3C8FE6B27DB3@microsoft.com... >> > Hello, >> > I write a Web Application: >> > its UI has a DataGrid controller. >> > The web application gets huge data from SQL Server, >> > then shows the result after processing these data. >> > >> > It needs much time to run it. >> > But, it happened an error after running less than 60 seconds. >> > This error didn't explain detail. >> > I set >> > Server.ScriptTimeout=600; >> > <httpRuntime executionTimeout="600" /> >> > cmd.CommandTimeout=600; >> > But, it doesn't work. >> > It still has an error in 60 seconds. >> > >> > How to solve it? >> > Thanks. >> > >> >> >>
It doesn't figure out what reason.
But, the data in the SQL Server is little, it could get the result. If the data is large, it will interrupt the execution. I Guess that it must run a long time, but ASP.NET doesn't allow it. Even though I set ScriptTimeout and CommandTimeout, it still doesn't extend the execution time. But, I think ASP.NET must can do it, only I don't know what to do. [quoted text, click to view] "Yunus Emre ALPÖZEN" wrote:
> Does your exception is thrown by SQL server or ASP.NET? Also if you set your > connection string timeout may your connection expire... > > -- > Thanks, > Yunus Emre ALPÖZEN > > > > "Grace" <Grace@discussions.microsoft.com> wrote in message > news:F5CD35B6-A976-4F07-8E19-5FB14915F646@microsoft.com... > >I don't configure the IIS setting. > > I already set ScriptTimeout and SqlCommand's CommandTimeout, but it > > doesn't > > work. > > The Web Page only needs a DataGrid which shows the processing result. > > So, I use Response.BufferOutput=false; , it still doesn't work. > > > > ASP Web Page can use Server.ScriptTimeout to extend running time, > > but ASP.NET seems no work for it. > > > > I think ASP.NET should have this function, but I don't find it until now. > > > > If you have other suggestions, please kindly tell me. > > Thanks. > > > > > > "Yunus Emre ALPÖZEN" wrote: > > > >> May your application have 60 seconds time out. which configured via IIS > >> manager. My advice you to test it using Response.BufferOutput is false. > >> and > >> flush it at some count of records. > >> > >> Also, i wonder if does it give a sql connection time out or ASP.NET > >> timeout? > >> If it gives a sql connection time out, you must set timeout in your > >> connection string... > >> > >> -- > >> Thanks, > >> Yunus Emre ALPÖZEN > >> > >> > >> > >> "Grace" <Grace@discussions.microsoft.com> wrote in message > >> news:9E4CA84B-5015-4B30-9D99-3C8FE6B27DB3@microsoft.com... > >> > Hello, > >> > I write a Web Application: > >> > its UI has a DataGrid controller. > >> > The web application gets huge data from SQL Server, > >> > then shows the result after processing these data. > >> > > >> > It needs much time to run it. > >> > But, it happened an error after running less than 60 seconds. > >> > This error didn't explain detail. > >> > I set > >> > Server.ScriptTimeout=600; > >> > <httpRuntime executionTimeout="600" /> > >> > cmd.CommandTimeout=600; > >> > But, it doesn't work. > >> > It still has an error in 60 seconds. > >> > > >> > How to solve it? > >> > Thanks. > >> >
[quoted text, click to view]
Grace wrote: > Hello, > I write a Web Application: > its UI has a DataGrid controller. > The web application gets huge data from SQL Server, > then shows the result after processing these data. > > It needs much time to run it. > But, it happened an error after running less than 60 seconds. > This error didn't explain detail. > I set > Server.ScriptTimeout=600; > <httpRuntime executionTimeout="600" /> > cmd.CommandTimeout=600; > But, it doesn't work. > It still has an error in 60 seconds. > > How to solve it? You could run the query in background and put the result into Cache or Application State. ASP.NET doesn't provide anything like servlet, but since the HttpApplication (global.asax) is not restarted per request, you may use it for the purpose. Just override HttpApplication.Init() to setup a thread for such tasks.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |