tracker issue : CF-3036947

select a category, or use search below
(searches all categories and all time range)
Title:

Bug 73952:(Watson Migration Closure)Schedule Tasks On Server Start

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/

Reporter/Name(from Bugbase): Ben Davies / Ben Davies (Ben Davies)

Created: 12/03/2008

Components: Scheduler

Versions: 9.0

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 /

Priority/Frequency: Normal / Unknown

Locale/System: English / Platforms All

Vote Count: 4

Duplicate ID:	CF-3034298

Problem:

Schedule Tasks On Server Start
<cfschedule interval="onServerStart" ... />
I would like ability to schedule tasks to run when the CF server starts (after the server has fully started and is fully available) 

See this thread: https://prerelease.adobe.com/project/forum/thread.html?cap=87529bda13744b3db718e841890b9240&forid={81302E9C-2163-4C37-9582-D9C14B236AE8}&topid={9CD6A3F8-E971-479C-A3B6-9FCCEF37845A}

This ER was raised for CF8 as 71067
Method:


Result:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3036947

External Customer Info:
External Company:  
External Customer Name: Ben Davies
External Customer Email: 447227C844C7765A992015A8
External Test Config: 12/03/2008

Attachments:

Comments:

+1 vote. I've needed this in the past (although the onServerStart event hook mitigates a lot of this for me).
Vote by External U.
24524 | November 10, 2011 07:05:32 PM GMT
this is an alternative to implementing an onServerStart() event.
Vote by External U.
24525 | November 10, 2011 07:05:33 PM GMT
I'm all for this one, but don't see a big interaction between it and the onServerStart() functionality. This ER is specifically aimed at schedule tasks, and runs *after* the server is up, which is an important distinction. Am important question about this ER's support is whether scheduled tasks that are not marked for running at startup, but become eligable to run (based on the time of day) would have to wait until all of the scheduled tasks marked to run at startup complete. It would be useful if this support allowed me to optionally mark a task as "run at start-up" or "run at start-up and block all non-startup tasks" so that I can be sure that blocks of jobs that run as a group are properly setup after a server restart that might have occured during their execution. There is a bit of overlap between this ER and the one for implementing scheduled task dependencies. This one is a good first step.
Vote by External U.
24526 | November 10, 2011 07:05:34 PM GMT
argh - I raised 71067 on January 6, 2008 and forgot to vote for this one. PLEASE!!!! B/c, the http service isn't available until 'after' the server is started.
Vote by External U.
24527 | November 10, 2011 07:05:35 PM GMT