A number of users are reporting problems with QueueMetrics being one hour off after DST came into effect on March, 11. This is caused by problems with the Java VM running QueueMetrics.
The United States has planned a change to its DST observance beginning in 2007. The Energy Policy Act of 2005 mandates that DST will start on the second Sunday in March and end on the first Sunday in November. In 2007, the start and stop dates will be March 11 and November 4, respectively. These dates are different from previous DST start and stop dates.
WHICH USERS ARE AFFECTED?This problem may be affecting you if your company, your servers or your call centers are located in either USA, Canada or another country or region which sets DST according to USA standards.
HOW DO I KNOW IF I AM AFFECTED?You will notice that since March 11 your QueueMetrics reports seem to be one hour off. You may also notice problems in the realtime pages.
This problem does not seem to affect everyone living in involved regions, likely because of the different JVMs used to run QueueMetrics and/or the way the clock is set on the server (as local time versus GMT).
HOW CAN THE PROBLEM BE FIXED?- Make sure your Linux box is aligned with the latest timezone data (on CentOS/RHEL, the package is named tzdata-2006m)
- Stop QueueMetrics
- Download the Sun JDK updater
- Run the updater with java -jar tzupdater.jar -u -v - if you installed QueueMetrics automatically, your Java to patch resides in /usr/local/queuemetrics/java
- Restart QueueMetrics
If you run a JVM from Sun, you can find the updater here:
http://java.sun.com/developer/technicalArticles/Intl/USDST/ (free registration required), while if you run a JDK from a different vendor you should check with your vendor for the timezone patch.
Please keep us posted if you encounter this problem or not, which versions of Java you are running and if you installed QueueMetrics manually or using yum.
Show Posts