Skip to main content
Inspiring
March 26, 2007
Answered

CFSchedule firing multiple times

  • March 26, 2007
  • 30 replies
  • 6932 views
Hi Everyone,
i still have not found a solution to this. if anyone has any other suggestions please let me know.
Also i would like to report this as a bug, what is the proper procedure for reporting this?

thanks to all

Tim

Original- Hi All,
i have had issues since upgrading from 6 to 7 with cfschedule. sometimes it runs fine, other times it will run the same task multiple times in a row, other times it will wait an hour then run the same task again.

This may not sound like a big deal, but the tasks send out several thousands of emails. talk about spam!!

I have been screamed at on a weekly basis to make this stop.

Now since the the DST change, the tasks that were scheduled at 3pm run at 3pm and again at 4pm!!

Please someone help!!!!!!!!!!!!!!!!!!!!!


Thanks in advance.
Tim
    This topic has been closed for replies.
    Correct answer nicetim
    Hi All,
    after restoring the system completly from backup, CF would not run.
    So we removed it completely and installed if from scratch.
    We restored the CFM code and database.

    This fixed it :) i guess i should have done this from the begining.
    So i have no idea what the issue was, lets just hope it does not come back.

    Thanks to all who gave suggestions and help,
    Good luck to those of you who are still having this issue, if you get tired of trying to find the solution, just format and start over.
    This was much less painfull than trying to fix this issue.

    Regards,
    Tim

    30 replies

    nicetimAuthor
    Inspiring
    July 30, 2007
    Hi BK,
    Yes this was done, i thought i posted it here, maybe i didnt.
    I tried this right after you posted it.

    I even deleted all the schedules restarted the whole box and just added one test schedule back in. on the page it calls is a cfmail tag, i got several emails from it.
    The task was to run once.

    Thanks
    tim
    BKBK
    Community Expert
    Community Expert
    July 30, 2007
    Nicetim, some time ago I wrote:
    "Why don't you note down the settings of the scheduled job. Then delete it from the Coldfusion Administrator. Restart the server. Register the scheduled job anew in the Coldfusion administrator. "

    Did you?

    nicetimAuthor
    Inspiring
    July 30, 2007
    Hi All,
    I feel your pain, the task i have that runs every 15 mins is a must have, which means i can only test something inbetween each task running. Also i spoke of cfif'ing out the date/time to make sure its only run once each quater hour, but the timing is off and this will cause unexpected results.

    I have tried affixing url params too

    I still do not have a solution for this agravating issue!!!

    Adobe are you reading this???

    I want to upgrade but have a fear that this issue would still be present.
    Also i dont think i should have to pay to upgrade just to fix something like this!!

    I need this fixed asap!!!

    BKBK
    Community Expert
    Community Expert
    June 8, 2007
    Dhays,
    I think it is sufficient to delete a scheduled job and restart the Coldfusion instance to make it go away forever.

    Known Participant
    June 8, 2007
    Thanks. That's what I would expect. I'll test that out in our dev environment and try to be a little more methodical in my approach. The hard part is scheduling downtime in production. This would be a lot easier than recreating the CF server.
    Known Participant
    June 8, 2007
    I still have this problem on one server. The latest thing I've noticed is the original schedules that I had tried to end by entering an end date and also by deleting, are still running. It seems that once a schedule is set up, it won't go away. It runs, reschedules itself and will continue forever.

    I may try creating a new CF server instance and putting the original, clean copy of the cfusion-ear in it. And then set everything up again.
    BKBK
    Community Expert
    Community Expert
    May 13, 2007
    i downloaded and ran the test script that link provides and my server passes the tests.
    Which is a good thing. I just thought of something.

    Why don't you note down the settings of the scheduled job. Then delete it from the Coldfusion Administrator. Restart the server. Register the scheduled job anew in the Coldfusion administrator.

    nicetimAuthor
    Inspiring
    May 12, 2007
    fyi,
    Also, this is was a fresh install on a freshly installed win2k3 box.
    we got two new boxes, i installed same version of everything on both, one production and the other is the development server.

    these are both CMFX7.02 with Flex enabled and installed as a multi server.
    We are not running multiple servers yet but i had planned on implementing it soon.

    I dont have verity turned on, but i am not sure about any other indexing service on our network.


    BKBK
    Community Expert
    Community Expert
    May 12, 2007
    Nicetim,
    Did you apply the U.S. Daylight Saving Time fix? It might help.


    nicetimAuthor
    Inspiring
    May 12, 2007
    Hi Guys,
    thanks for all the posts and suggestions.

    I have a workaround for this issue by CFIF'ing the date/time is not correct to aboart but thats just a bandade.

    I ran the DST update a while back, but i have SUN JVM version 1.4.2_13-b06
    I had some other issue a while back and the fix was to use a different jvm.

    This is probably the whole problem but i dont want to go back unless someone is sure this is the issue.

    Is there a more updated jvm i can be using?

    thanks again everyone
    Tim
    Known Participant
    May 11, 2007
    I installed the 1.4.2_11 JRE and the schedules are only firing once. I read somewhere in the forums or tech notes that 11 is the latest certified version. I think it was certified for the recent DST issue. Remeber that this fix includes the latest hot fix, chf7020002. I'll be testing for a day or 2 before upgrading production.
    May 11, 2007
    Yo Dunc, I don't think that 7 supports the 1.5 or 1.6 JRE. That's one of the things which CF 8 will address, as I understand it. I know that doesn't help, as you're just now moving to 7...

    I agree that it's probably related to something in the upgrade process. Best of luck.

    I love that I can include a beer emoticon.

    Cheers,
    Steve
    Known Participant
    May 11, 2007
    My latest test was to edit the jvm.config file to use the default JRE that installs with CFMX7, 1.4.2_09-b05. I had installed a newer JRE, 1.4.2_13-b06, to please our security staff.

    Surprisingly, at least to me, this seems to have solved the problem! The odd thing is that the server that had the fresh install is using 1.4.2_13-b06 and does not have the problem. I'll post again once I can confirm that this really is a solution.

    One note on JRE's, I had tried versions of 1.5 and 1.6 only to find that Verity did not work with them. That's why I backed off and was using the latest version of 1.4.2 that I could find at the time.