JDK-4092412 : JVM sets user.timezone incorrectly.
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 1.1.4
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_2.6
  • CPU: x86
  • Submitted: 1997-11-12
  • Updated: 1998-03-02
  • Resolved: 1998-03-02
Related Reports
Duplicate :  
Description

Name: rm29839			Date: 11/12/97


JDK 1.0.2 Date class used native methods to handle
timezone issues.  JDK 1.1.4 uses TimeZone class
which defines timezone tags which do not match
that used in the zoneinfo database.  

In the case of Australia, the JVM initializes
user.timezone to EST, but according to TimeZone.java
that is somewhere in the U.S.  AET is TimeZone.java's
tag for Australian EST, but nothing else uses it.

It would be much better if the JVM initiallized
user.timezone to GMT[+-]nnnn and ignore
the issue of timezone names - or go back to using
a native method that does the right thing.

Given all the above - and the fact that there
appears to be _no_ documented standard (or default)
location for properties that Java will load, JDK 1.1.x
is totally broken in this regard.
(Review ID: 19556)
======================================================================

Comments
WORK AROUND Name: rm29839 Date: 11/12/97 Either go back to using localtime(), introduce a standard properies lication - and document it or just set user.timezone to GMT[+-]n ======================================================================
11-06-2004