Adobe Community: Daylight Savings Time; running scheduled tasks on time

Currently Being Moderated

1. kylemurphy2009,

Nov 8, 2010 2:10 PM in reply to sroberts7101

Report

Did you ever figure this out? We are using a different JVM than what ships with CF8 (1.6.0_14) and we see the same behavior. It appears to only be the daily frequency jobs. In my case, when we fell back this weekend, I had a job that runs at 12:01am. It ran at 12:01am on Sunday, but then the log shows that it rescheduled it to run at 11:01PM on the same day. So, it's clearly adding 24 hours and then compensating for the hour gained during the switch to Savings time.

When we lose an hour in the spring, it simply does not schedule the jobs for a full day, so a day skips.

Again, I don't think it's a JVM issue, but I can't believe that no one else is having this issue and I can't find anyone talking about it.

Thanks,

Kyle

|

Mark as:

Currently Being Moderated

2. sroberts7101,

Nov 9, 2010 5:36 AM in reply to kylemurphy2009

Report

Hi Kyle,

Well, I'm happy to see that I'm not the only person in the world trying to figure this out, so for that, Thank you.

We have not figured out what to do about this, other than to use GMT and not change the time at all. Since the servers are located in the Eastern Time Zone, that solution makes scheduling new tasks very confusing.

We have noticed that this past weekend, we have no issues with the tasks running late, early, twice or not at all. It only happens in the Spring when we lose an hour. My only other thought is to tell the OS not to adjust the clock automatically, and adjust the clock manually Sunday afternoon after all of the tasks have had their run and when we have a window larger than an hour with nothing scheduled. This way, they're all scheduled properly since CF already adjusted the task for its next run time...Or, do we ever need to adjust the clock in the OS if CF already took the adjustment into consideration?

As of now, I haven't figured anything out for sure, and really don't like testing on production systems. Too bad we can't just turn the change off in CF or Java...or can we?

|

Mark as:

Currently Being Moderated

3. kylemurphy2009,

Mar 12, 2012 12:28 PM in reply to sroberts7101

Report

Did anyone ever figure out how to fix this? This is the first forum/blog posting about this issue that I've found and I've been looking for years.

I am seeing these same exact symptoms. I have 200+ scheduled tasks that run perfectly fine, but twice a year we have issues. It eventually fixes itself, but for the 24-48 hours after a time change it wreaks havoc on me.

Does CF9 fix this? I've read a post on Ben Nadel's log about storing my tasks in the database, but I really don't want to have to go through all of that trouble because of a seemingly simple bug. I guess not many people use Scheduled Tasks like we do.

Here is Ben's post in case you were wondering:

http://www.bennadel.com/blog/2237-Storing-Your-ColdFusion-Scheduled-Ta sks-In-The-Database.htm

|

Mark as:

Currently Being Moderated

4. carl type3,

Mar 12, 2012 7:07 PM in reply to kylemurphy2009

Report

Maybe define the current timezone will fix the problem.

Start up CF JVM with the following eg:

JVM Arguments

-server -Dsun.io.useCanonCaches=false -XX:MaxPermSize=192m -XX:+UseParallelGC -Dcoldfusion.rootDir={application.home}/../ -Dcoldfusion.libPath={application.home}/../lib -Duser.timezone=Australia/Sydney

Your timezone parameter will likely differ to Sydney. You may have other JVM settings pertinent to your environment with different perm and garbage collector settings. Can be a good idea to backup your JVM.CONFIG before applying any JVM changes.

HTH, Carl.

|

Mark as:

ColdFusion Server Administration

Daylight Savings Time; running scheduled tasks on time

Mar 17, 2010 10:55 AM

More Like This

Bookmarked By (0)

Answers + Points = Status