tracker issue : CF-4163333

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

Do not allow special characters in scheduled task names if scheduler cannot handle them

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/CannotReproduce

Reporter/Name(from Bugbase): John Walker / John Walker (John Walker)

Created: 06/10/2016

Components: Administrator

Versions: 11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Minor / Unknown

Locale/System: English / Win 2008 Server R2

Vote Count: 0

I thought my scheduler XML was corrupt, but it the problem was caused by having / and - and , in the scheduled task names. It caused some of them to show as Expired even though they were active.  It caused errors when deleting the scheduled task, the update could not find the record to update - but I could not add another one, I received an error that the task already existed.

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

Watson Bug ID:	4163333

External Customer Info:
External Company:  
External Customer Name: John Walker
External Customer Email:  
External Test Config: My Hardware and Environment details: CF11 Enterprise running on Dell servers using VMware.  Windows 2008R2

Attachments:

Comments:

HI John, I tried with a schedule task that had '/' and '-' in the task name,but failed to reproduce it. Can you provide us your neo-cron.xml file ? Can you also tell us which update are you on? This would be helpful for us to get a repro case! Thanks, Suchika P.S. neo-cron.xml would be present in <cfinstancedir>/lib .
Comment by Suchika S.
2448 | June 13, 2016 04:06:49 AM GMT
Hi John, Are you still facing the issue? Please send us the neo-cron.xml if you are still facing the issue. Thanks, Suchika.
Comment by Suchika S.
2449 | August 05, 2016 01:26:02 AM GMT
John, can you send us the file?
Comment by Vamseekrishna N.
2450 | August 18, 2016 01:45:39 AM GMT
@John, we are closing this bug as we are not able to reproduce the issue. If you have additional information to help us move on this, do let us know.
Comment by Vamseekrishna N.
2451 | August 24, 2016 12:00:34 AM GMT