tracker issue : CF-4104009

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

neo-cron.bak should not be generated after task execution

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/NotABug

Reporter/Name(from Bugbase): Stephen Rittler / Stephen Rittler (Stephen Rittler)

Created: 01/05/2016

Components: Scheduler

Versions: 11.0

Failure Type:

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Win 2012 Server x64

Vote Count: 0

Problem Description:
neo-cron.bak should only be updated when the task parameters are updated so we can see what changed and when. It appears that the backup file is re-created every time the task runs in order to update the last run date/time. I expect that neo-cron.bak would only be updated if the frequency, url, task name, or auth credentials change for the task.

Steps to Reproduce:
Schedule a task.
Take note of the timestamp on neo-cron.bak.
Let the task run.
Verify that neo-cron.bak is updated after the task is run.

Actual Result:
neo-cron.bak is updated unnecessarily

Expected Result:
neo-cron.bak remains unchanged after task execution

Any Workarounds:
none known

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

Watson Bug ID:	4104009

External Customer Info:
External Company:  
External Customer Name: Stephen Rittler
External Customer Email:  
External Test Config: My Hardware and Environment details:

windows server 2012, cf11hf6



Hi Stephen, I find the "last ran" timestamp to be useful information. I would not want the "Last Run" column to be removed from CF Admin, nor "result.lastfire" to be removed from cfschedule(action="list",..) (and same for Admin API's equivalent). That said, I've experienced times when neo-cron.xml becomes 0 byte - and I'd hope that issue would be resolved. Just mentioning all this as I'm not sure if you're also running into the 0-byte issue or if you also feel the Last Ran info isn't useful. Thanks!, -Aaron
Comment by External U.
4948 | January 06, 2016 05:35:46 PM GMT
Hi Stephen, The file is being backed up to update "lastran" info & "lastran" info is important for a task. Hence, this is not a bug and so closing it. Thanks, Suchika.
Comment by Suchika S.
4949 | January 07, 2016 06:21:14 AM GMT
I agree that lastran is useful but i'm suggesting that it's not an update that should trigger the backup of the neo-cron file. Update neo-cron.xml, but don't update neo-cron.bak. An updated timestamp is not a meaningful configuration change.
Comment by External U.
4950 | January 07, 2016 09:17:24 AM GMT