Status/Resolution/Reason: Closed/Fixed/Fixed
Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)
Created: 11/02/2016
Components: Scheduler
Versions: 2016
Failure Type:
Found In Build/Fixed In Build: CF2016_Update3 / 2020.0.0.314698
Priority/Frequency: Major / Some users will encounter
Locale/System: English / Win All
Vote Count: 0
When cfschedule creates a task w/ handler, CF stores the full system path (i.e. C:\path\to\handler.cfc) to the handler in neo-cron.xml. Good. This was done per 4126563, so that these tasks could be later edited via CF Admin.
However, CF Admin's "Add/Edit Scheduled Task" page does not have a form field for specifying the handler's full system path. After creating a new task w/ handler in CF Admin, an error is logged to scheduler.log whenever the task fires. This is b/c CF Admin stored the dot-delimited path as the full system path in neo-cron.xml.
Steps to Reproduce:
1) In CF Admin, create a new task w/ handler
2) In neo-cron.xml, see the task's "eventhandler" and "eventhandlerrp" values match (bad)
3) When firing the task, see an error is logged to scheduler.log (bad)
Suggestions:
1) Allow cfschedule's eventhandler attribute to accept a full system path (i.e. C:\path\to\handler.cfc).
2) Allow the Event Handler field, on CF Admin's "Add/Edit Scheduled Task" page, to accept a full system path (i.e. C:\path\to\handler.cfc).
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 4197252
External Customer Info:
External Company:
External Customer Name: Aaron Neff
External Customer Email:
Attachments:
- August 03, 2017 00:00:00: 4197252_20170803.zip
Comments: