US DST Changes impact in Applications Manager

The latest version of Applications Manager ( from Build Number 7100 ) uses JRE 1.5 update 6. The older versions uses JRE 1.5. Due to the recent DST ( Daylight Savings Time ) changes in US, for Java 1.5 version - JREs older than update 6 has to be updated. So customers having old version of Applications Manager ( before build 7100 ) have to update the java timezone database bundled with java in Applications Manager.

Checking the bundled Java Version

To check if you need to update the java, go to AppManager7\working\jre\bin directory from the command prompt and execute the following command,

For Windows
java -version

For Linux
./java -version

Please update, if you get the below output

java version " 1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing)

Please do not update, if you get the below output

java version " 1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)

Steps for Applying the Java fix :

We assume your OS is already patched for this problem. Refer here for more information : Microsoft, Redhat

1. Stop Applications Manager and open a command prompt. Go to Appmanager7 directory and execute the following command,
For Windows
shutdownApplicationsManager.bat -force
For Linux
sh shutdownApplicationsManager.sh -force
2. Download JDK US DST Timezone Update Tool ( tzupdater-1_0_1.zip file ) from java.sun.com/javase/downloads/index.jsp and extract the zip in your machine.
3. Copy tzupdater.jar (a file that exists in the downloaded tzupdater-1_0_1.zip file) to AppManager7\working\jre\lib directory.
4. Download the dstupdater.bat.txt ( for windows ) or dstupdater.sh.txt ( for linux ) attached in this forum. Rename the file as dstupdater.sh/bat and save it in your AppManager7\working\jre\bin directory.
5. Open a command prompt and go to AppManager7\working\jre\bin directory.
6. Execute dstupdater.sh/bat file there.

Verifying the Java fix applied :

To check if you have applied the above java fix correctly you can follow the below steps,

1. Download the PrintTimeZone.class.txt attached in this forum. Rename the file as PrintTimeZone.class and save that file in your AppManager7\working\jre\bin directory.
2. Then open a command prompt, go to AppManager7\working\jre\bin directory and execute the following command
For Windows
java PrintTimeZone
For Linux
./java PrintTimeZone
3) If you get the below output the fix has been applied correctly,

Zone ::sun.util.calendar.ZoneInfo[id="US/Pacific",offset=-28800000,dstSavings=3600000,useDaylight=tr
ue,transitions=185,lastRule=java.util.SimpleTimeZone[id=US/Pacific,offset=-28800000,dstSavings=36000
00,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=72000
00,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]]

4) If you get the below output, there is some problem in the fix applied or it has not been applied yet . So try to apply the fix again.

Zone ::sun.util.calendar.ZoneInfo[id="US/Pacific",offset=-28800000,dstSavings=3600000,useDaylight=tr
ue,transitions=185,lastRule=java.util.SimpleTimeZone[id=US/Pacific,offset=-28800000,dstSavings=36000
00,useDaylight=true,startYear=0,startMode=3,startMonth=3,startDay=1,startDayOfWeek=1,startTime=72000
00,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]]