Title:
Bug 73885:(Watson Migration Closure)There are a handful of great ideas already submitted for improving the use of the CF task scheduled in production environments
| View in TrackerStatus/Resolution/Reason: Closed/Deferred/
Reporter/Name(from Bugbase): Reed Powell / Reed Powell (Reed Powell)
Created: 12/01/2008
Components: Scheduler
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Major / Unknown
Locale/System: English / Platforms All
Vote Count: 0
Problem:
There are a handful of great ideas already submitted for improving the use of the CF task scheduled in production environments. I'd like to add a request for the ability to monitor the status of tasks, beyond the ability to know when the last ran/started/completed.
The ability for tasks to post status information in a manner that can be easily retrieved/reported would be great. I currently use a jerry-rigged combination of application names and uniformly named session vars to store status/progress information in a task, and Java calls in a display app to retrieve and report it all - being able to use a cleaner approach (even if I still need to write the app that displays the data) would make this a much more stable setup. Being able to retrieve this data with the Admin API (using CF STANDARD!) would be a step in the right direction. The trick of course it to be able to keep that info after the task has completed, at least until the next time it executes, and to not lose it across server restarts (currently a problem with my setup).
The bottom line is that scheduled tasks are a powerful tool in a production environment that uses the CF feature set to do a lot of data processing, and being able to know what those tasks are up to is important.
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3036911
External Customer Info:
External Company:
External Customer Name: Reed Powell
External Customer Email: 0C7666B046112672992015D5
External Test Config: 12/01/2008
Attachments:
Comments: