HiTek Software Home
 
Title Schedule is 1 hour off in some time zones
Date Updated 12/08/2005
Versions affected JavaScheduler 2.5+, Automize 4.0+
OS affected All 
Description In some Australian time zones and some other time zones, scheduled events do not run at the allocated time, but are off by an hour.  
Causes This is an issue with the Sun's Java Machine (JRE 1.3).  The Automize scheduler engine which runs all Automize tasks is written in Java and uses JRE 1.3.0  This issue is documented in the following articles:
http://developer.java.sun.com/developer/bugParade/bugs/4505478.html

http://developer.java.sun.com/developer/bugParade/bugs/4506134.html

This problem is supposedly fixed in Sun's JRE 1.3.1 and later.  Some of these problems in 1.3.0, were due to the fact that these time zones had special rules in year 2000, and changed in 2001.  1.3.0 was released in 2000, and used the old 2000 rules.  1.3.1 was released in 2001, and uses the updated rules.

Solution There are two solutions to this issue:

1) Windows users only: Use a workaround.  Set your computer clock to 'automatically adjust for daylight savings time'
Please visit the following knowledge base article to see how::
Title = Automize time is 1 hour off in TimeZones that have daylight savings time
Current URL = Automize time is 1 hour off in TimeZones that have daylight savings time
Please inform us if this URL is outdated.

2) Uses the latest versions of the JavaMachine.  This problem is supposedly fixed in Sun's JRE 1.3.1 and later. Download and use JRE 1.3.1 or JRE 1.4.x. 

Please visit the following knowledge base article to download and use one of the above two JRE's:
Title = Running Automize in the latest java machine
Current URL = Running Automize in the latest java machine

Please inform us if this URL is outdated.

Output Log -
Debug Log

-