M
Marcin Belczewski
I have ASP.NET page that invokes a stored procedure in the database.
It takes about 60 seconds for the stored procedure to complete.
In web.config I have <httpRuntime executionTimeout="10"/> and
<compilation debug="false" /> so I expect that "timeout expired" whill
show up in the browser after 10 seconds.
Unfortunately ASP.NET page doesn't show the "timeout expired"
information in the browser after 10 seconds!
The information is shown once stored procedure is fininshed which is
about 60 seconds!!
Why ASP.NET doesn't show "timeout expired" after 10 seconds but waits
until database call is completed?
Is that because database drivers are unmanaged and ASP.NET cannot
interrupt such call?
Mabsky
It takes about 60 seconds for the stored procedure to complete.
In web.config I have <httpRuntime executionTimeout="10"/> and
<compilation debug="false" /> so I expect that "timeout expired" whill
show up in the browser after 10 seconds.
Unfortunately ASP.NET page doesn't show the "timeout expired"
information in the browser after 10 seconds!
The information is shown once stored procedure is fininshed which is
about 60 seconds!!
Why ASP.NET doesn't show "timeout expired" after 10 seconds but waits
until database call is completed?
Is that because database drivers are unmanaged and ASP.NET cannot
interrupt such call?
Mabsky