timezone - IBM vs Oracle/Sun JDK, java.util.Timzone getOffset () behaving differently -
ibm vs oracle/sun jdk, java.util.timzone behaving differently ,
ibm jdk 1.5 vs sun/oracle jdk 1.6
import java.util.*; class timetest { public static void main(string args[]){ long = system.currenttimemillis(); system.out.println("est : " + timezone.gettimezone("est").getoffset(now)); system.out.println("us/eastern : " + timezone.gettimezone("us/eastern").getoffset(now)); } } ***ibm jvm ouput est : -14400000 us/eastern : -14400000 oracle jvm est : -18000000 us/eastern : -14400000 ibm jdk java -version java version "1.5.0" java(tm) 2 runtime environment, standard edition (build pxi32devifx-20090811 (sr10 +iz56666+iz56751)) ibm j9 vm (build 2.3, j2re 1.5.0 ibm j9 2.3 linux x86-32 j9vmxi3223-20090707 (jit enabled) j9vm - 20090706_38445_lhdsmr jit - 20090623_1334_r8 gc - 200906_09) jcl - 20090811 oracle jdk java -version java version "1.6.0_24" java(tm) se runtime environment (build 1.6.0_24-b07) java hotspot(tm) client vm (build 19.1-b02, mixed mode, sharing) update , tested ibm jdk 6 , matches ouput of oracle/sun java -version java version "1.6.0" java(tm) se runtime environment (build pxi3260sr6ifix-20091015_01(sr6+152211+155930+156106)) ibm j9 vm (build 2.4, jre 1.6.0 ibm j9 2.4 linux x86-32 jvmxi3260sr6-20091001_43491 (jit enabled, aot enabled) j9vm - 20091001_043491 jit - r9_20090902_1330ifx1 gc - 20090817_aa) jcl - 20091006_01
java timetest est : -18000000 us/eastern : -14400000***
i think it's safe ibm jdk install has older timezone database other jdk installs. jdk 1.5 released in 2004.
Comments
Post a Comment