Scheduled Tasks not chaining

[ggantzer2]

Hello,

We are using CF10 and have setup a series of chained scheduled tasks. We tested them manually by starting the first process from the admin, and all three processes ran. When the first process triggers at its daily time, it wont kick off the second chained process. No error is produced that i know of.

We also attempted to trap the error by invoking an event handler on exception and misfire, but we're unable to get the scheduler to find the cfc regardless of the syxtax we use. The site is setup as a subdomain for another site, but it is still a distinct site. We placed the CFC in the root of both the subdomain site and regular www site and tried several paths, but none seem to work. For example, the site is located in d:\web\site.com\subDomain. We tried setting the event handler path as web.site.com.subDomain.handlerCFCName, site.com.subDomain.handlerCFCName, subDomain.handlerCFCName and handlerCFCName, and none worked.

Any help on either topic is greatly appreciated.

[Carl Von Stetten]

ggantzer2,

Have you used the new Server Updates feature in CF10 to apply the Update 1 (10.0.1) that just came out?  I believe it included several fixes related to scheduled tasks.  You can install the update from inside the CF Administrator (expand the Server Update section in the left-side navigation panel, then select Updates).  If you havent' done it yet, try the update and see if it resolves your issues.  If not, reply back and I'm sure someone will jump in with some further suggestions.

-Carl V.

[ggantzer2]

We did put the patch in, no change. Havent rebooted the server since, but i dont think it required it.

[hemant_k1]

A server restart is required after applying the patch. Can you please log a bug on http://bugbase.adobe.com/ to report the details of issue to us?

[vamsee_k]

We have logged a bug and are tracking this issue here:

https://bugbase.adobe.com/index.cfm?event=bug&id=3327936

[ggantzer2]

Thank you for submitting this. The second portion of the bug related to trapping the error was solved, but the chaining remains an issue. For the second portion, a directory in the CFC path contained a “.”, such as “c:/site/site.com/ “, which could not be handled by the CF Admin. We mapped a new path in the administrator to correct this.

Greg Gantzer

Gantzer Group, Inc

<mailto:greg@gantzer.net> greg@gantzer.net

(216) 916-0507 phone

(216) 244-2287 mobile

(330) 929-9211 fax