tracker issue : CF-3364274

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

cfschedule's onMisfire attribute is case sensitive for FIRE_NOW

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Rob Bilson / Rob Bilson (Rob Bilson)

Created: 11/12/2012

Components: Scheduler

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final / 283349

Priority/Frequency: Major / Most users will encounter

Locale/System: English / Windows 7 64-bit

Vote Count: 0

Problem Description: The onMisfire attribute of cfschedule is case-sensitive for FIRE_NOW.  Unless you specify REFIRE_NOW in all caps, the onMisfire event never fires.

Steps to Reproduce:
Execute the following code, which will setup a task to run one minute from when you run it.  Then stop your ColdFusoin server service for a few minutes.  Restart, log into the CF Admin and observe that the task hasn't executed (last run time is never, and log doesn't show misfire/execution.

<cfschedule 
	action="update"
	task="OnMisfire_Fire_Now"
	url="http://localhost/cf10wack/14/myTask.cfm"
	startdate="#now()#"
	starttime="#dateAdd('n', 1, now())#"
	interval="daily"
	onmisfire="fire_now" 
/>

Now, change onmisfire to onmisfire="FIRE_NOW" and repeat the procedure. This time, you'll see that after restarting the server, the task does indeed refire.  Checking the CF Admin shows the last run time and checking the scheduler.log shows that the task has both misfired and then refired.

Actual Result:
Expect the misfired task to refire.

Expected Result:
Task never refires.

Any Workarounds:
The workaround is to use FIRE_NOW and not fire_now.

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

Watson Bug ID:	3364274

External Customer Info:
External Company:  
External Customer Name: Rob Brooks-Bilson
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments: