Booya! That totally worked! Thanks a lot for your help Alan and thank you everyone else for your continued development of OpenBD. Greatest thing since sliced bread?
On Sep 23, 3:35 pm, "Alan Williamson (aw2.0 ltd)" <[email protected]> wrote: > Fixed. > > I invoked a nightly build (early) and you can download the latest > OpenBlueDragon.jar from the main download site and copy it over the top > of the last one. > > __background__ > > This was a wee subtle one -- the startdate was way in the past, and the > routine to calculate when the task is to begin next, was basically > looping around right up to the current date -- hence the CPU max out rate. > > This area of the code has had many hands on it over the years as we > learned more and more about how other well known (some would say market > leaders) CFML engines managed their scheduling. It is an area, that one > day, we'll completely refactor and go at again. > > Personally, i find the cron-tab plugin way more useful and easier to > setup than CFSCHEDULE. If only they took a more crontab approach to > this area, a lot of confusion would have been lifted for developer and > engine maker a like! :) > > > > Peter J. Farrell wrote: > > >> I have recreated this ... looking into now ... watch this space > > And Alan to the rescue! Such a rock star! Watching here too. > > > Alan, if you could give a small history if you figure out the issue -- > > I'd appreciate it. I'm trying to get a better handle on the code base > > for OpenBD. > > > .pjf -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
