We have ColdFusion 10 installed on Windows Server 2008 with IIS 7.5.
We are running one additional instance of Coldfusion seperate from the cfusion instance but on the same physical server. Our scheduled tasks, on this instance, had been running without any problems for quite some time now. Suddenly about 3 weeks ago after a server reboot our tasks stopped running. We have tried everything including writing the output to a log file. The only thing that gets written to this log file is "Connection Failed".
Driling down into some of the other CF logs we are seeing that the job is getting triggered and then the job starts but it never gets completed.
Nov 6, 2013 16:01:00 PM Information [DefaultQuartzScheduler_Worker-6] - Task DEFAULT.sampleTask triggered.
Nov 6, 2013 16:01:00 PM Information [DefaultQuartzScheduler_Worker-6] - Starting HTTP request {URL='https://ru.ryerson.ca:443/ryecast/myTask.cfm', method='get'}
The weird thing is that if we create the same task in the instance manager (cfusion) on the same server pointing to the same .cfm file it works fine. So we know the script does work - just not in the ColdFusion Instance we need to work in.
Here is the successful log entry from cfusion logs.
Nov 6, 2013 16:01:00 PM Information [DefaultQuartzScheduler_Worker-6] - Task DEFAULT.sampleTask triggered.
Nov 6, 2013 16:01:00 PM Information [DefaultQuartzScheduler_Worker-6] - Starting HTTP request {URL='https://ru.ryerson.ca:443/ryecast/myTask.cfm', method='get'}
Nov 6, 2013 16:01:00 PM Information [DefaultQuartzScheduler_Worker-6] - HTTP request completed {Status Code=200 ,Time taken=124 ms}
Has anyone else experience this kind of behaviour and if so is there a fix? I suspect some kind of corruption with the QuartzScheduler.