Status/Resolution/Reason: Closed/Withdrawn/Duplicate
Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)
Created: 03/23/2012
Components: Scheduler
Versions: 10.0
Failure Type:
Found In Build/Fixed In Build: Public Beta /
Priority/Frequency: Major / Some users will encounter
Locale/System: English / Win All
Vote Count: 0
Duplicate ID: CF-3141655
I noticed paused tasks log a "misfire" when CF starts. Just pause 1+ tasks, then restart, then see misfires in scheduler.log. A paused task should only log a misfire when it is resumed. But if a task is paused before CF start, then it should not log a misfire when CF starts (b/c it is still paused at this point). Seems like something wrong is happening when the scheduler initializes?
Repro:
<cfschedule action="update" task="MyTask" startdate="#dateFormat(now(), ’DD/MM/YYYY’)#" starttime="#timeFormat(now(), ’hh:mm tt’)#" interval="30" url="http://localhost/nonexistentpage.cfm" />
<cfschedule action="pause" task="MyTask" />
Steps:
1) Run above code
2) See no entry added to scheduler.log
2) Restart CF
3) See the following entry in scheduler.log:
scheduler.log said:"Information","DefaultQuartzScheduler_QuartzSchedulerThread","03/17/12","05:14:09",,"Task DEFAULT.MYTASK misfired."
On a related note: As for why Quartz thinks a resumed task, which missed a fire time while paused, should trigger a misfire: I dunno. IMO, all fire times should be ignored while paused. But yeah I was referring to while-still-paused.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3146083
External Customer Info:
External Company:
External Customer Name: itisdesign
External Customer Email:Attachments:
Comments: