tracker issue : CF-4086307

Problem Description: Coldfusion is filling up its scheduler.log and exception.log with invalid "Task Invokehandler could not be chained" error messages.

Steps to Reproduce: see 'Test Configuration' section for my complete write-up of the problem

Actual Result: Scheduled Tasks creating many invalid 'error' lines in the logs EVERY time ANY scheduled task (that was migrated from CF9 into CF11) is run. (No errors are reported if that same task is created from scratch using CF11).

Expected Result: Scheduled Tasks should create no invalid 'error' lines in the logs.

Any Workarounds: delete all prior CF scheduled tasks and re-enter them from scratch

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

Watson Bug ID:	4086307

External Customer Info:
External Company:  
External Customer Name: Byron H Knapp
External Customer Email:  
External Test Config: Hi, 

PROBLEM:

Coldfusion is filling up its scheduler.log and exception.log with invalid "Task Invokehandler could not be chained" error messages.



ADDITIONAL INFO: 

We have about 150 scheduled Coldfusion tasks that were setup in CF9. We then migrated from CF9 to CF11 (using the normal Adobe migration tools/procedures). We experienced no problems with the migration process.



All the scheduled tasks seemed to migrate OK (there is a new field on the CF11 scheduler properties screen called "chained task". It is blank.). All of these tasks run fine. 



However, there is invalid "error" information added to both the scheduler and exception logs EACH TIME one of these scheduled tasks runs. Below I have included the log snips of a sample "error". (Each error creates SIX additional lines in the exception.log!) 



Then, as a test, I add a NEW scheduled task. I make it identical to one of those converted tasks, except that the new task runs at a slightly different time.



This NEW task works fine and it does NOT log error messages. The only difference is that it was created with CF11 (instead of being created with CF9 and then migrated to CF11).



And finally, if I bring up one of those 150 tasks inside the CF Scheduled Task GUI, and then I make a minor change to its properties (like adjusting the time it runs), and then SAVE the properties screen, the problem does NOT go away (in case you are wondering, as I did, if that would fix it). 



Any ideas how I can fix my scheduled tasks from filling up my logs, so I don't have to delete, and then re-enter 150 tasks?

Thanks!

Byron_K

-----------------



LOG SNIP for SCHEDULER.log



"Information","DefaultQuartzScheduler_Worker-6","11/10/15","17:51:02",,"Task DEFAULT.My-Task"

"Error","DefaultQuartzScheduler_Worker-6","11/10/15","17:51:02",,"Task invokehandler could not be chained"

. . . . . . . . . . . . . . . . . . . . . . . . .



LOG SNIP for EXCEPTION.log



"Error","DefaultQuartzScheduler_Worker-6","11/10/15","17:51:02",,"Task DEFAULT.My-Task"

java.lang.Exception: Task invokehandler could not be chained

	at coldfusion.scheduling.CronTask.onCompleteTask(CronTask.java:215)

	at coldfusion.scheduling.CronTask.execute(CronTask.java:130)

	at org.quartz.core.JobRunShell.run(JobRunShell.java:207)

	at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:560)

Attachments:

Comments: