Process Timeout, Running tasks outside of scheduler.

Discussion in 'Hosting Services / Control Panel' started by FlyTheBlueSky, Mar 10, 2008.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. I have some jobs that need to be run daily and I use the scheduler service for those. However, there are some jobs I need to run that can take anywhere from 2 to 15 minutes to complete - most of the time is spend waiting on a remote server to generate a report. The problem is that the report times out after 5 minutes, so when the DASP scheduled job runs it may or may not be around to catch the completed job from the remote server.

    For various reasons I do not want this task to be initiated from some other server.

    Is there someway I can get a thread to fire outside the regular 15 minute scheduler intervals, or does DASP have virtual hosting services or something else I could use for these sorts of tasks?

    Thanks!

    P.S. I've been with DASP for nearly a year now... keep up the good work! Thanks.
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    I think you misunderstood how the scheduler works. The scheduler service simply make a http call to the page you specified, it does not wait for a response.

    If you are seeing timeout, it is timing out from your site's page.

    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  3. I am having the same issue. My task, when started from a browser, take approximately 10 minutes to run, but runs to completion successfully. When started from the scheduler, the Last Result line says reads Timeout. Where is the timeout result coming from? If something is timing out my task, any idea how can I get around this?

    Thanks
     
  4. The scheduler service has been updated since the first post. It now waits 90 seconds for the complete response from the page. The scheduler obviously can't wait forever, but a timeout does not necessarily mean that your script failed to run. Since the http call was already made, it most likely ranto completion on the server side. So if your script takes about 10 minutes to run, you will always see a timeout as a result.

    Aristotle

    DiscountASP.NET
    www.DiscountASP.NET
     
  5. Thanks for the update
     
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