Timeout for Scheduled Tasks

Discussion in 'Getting started' started by rsmith720, Jan 20, 2010.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. This question may have been answered in the past, but I could find anything on the subject.

    Q: Does the same server time-out period also apply with scheduled tasks similar to running asp/x pages via the web browser? IE. If I call the task page via a web browser and if it takes longer than the default 90 seconds to complete it times out. Does this same stipulation apply to the pages when called via the control panel task scheduler?

    I ask because the job I run nightly could take anywhere from 5-15 minutes to finish processing and for fear of timing out I have been manually running it until I am confident it will run successfully regardless of how long the job takes to complete.

    Thanks,

    Roger
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    the timeout is controlled by the asp.net application.

    The schedule task tool will make a HTTP call to the page and the page will continue to run until the timeout setting in your application is reached.
     
  3. That's what I figured, thanks. In classic ASP I currently have the timeout set to server.ScriptTimeout = 6500, which I believe is approximately 10.8 minutes.

    Isn't the value passed in server.ScriptTimeout in tenths/twips of a second? I am pretty sure it isn't seconds because I have had it time out long before 108 minutes with this setting. What, if any is the maximum value that can be passed to the server.ScriptTimeout variable?

    Thanks

    PS. I know that the server.ScriptTimeout is a 32 bit signed integer which would basically equate to 68 years... but I just want to know if DASP has any max set for these timeouts.
     
  4. That's what I figured, thanks. In classic ASP I currently have the timeout set to server.ScriptTimeout = 6500, which I believe is approximately 10.8 minutes.

    Isn't the value passed in server.ScriptTimeout in tenths/twips of a second? I am pretty sure it isn't seconds because I have had it time out long before 108 minutes with this setting. What, if any is the maximum value that can be passed to the server.ScriptTimeout variable?

    Thanks

    PS. I know that the server.ScriptTimeout is a 32 bit signed integer which would basically equate to 68 years... but I just want to know if DASP has any max set for these timeouts.
     
  5. Bruce

    Bruce DiscountASP.NET Staff

    ScriptTimeout value is second.
     
  6. Thanks for the correction Bruce... but that doesn't answer my question.

    Additionally, with a setting of 6500 (seconds) which is approximately 108 minutes, why then when I run a test on DASP does the test page time out in about 10 minutes?
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page