JDK-5055567 : (tz) TimeZone.getAvailableIDs(int) may produce inconsistent info with getRawOffset()
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-06-01
  • Updated: 2006-02-23
  • Resolved: 2004-10-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b07Fixed
Related Reports
Relates :  
JDK-6380023 - (tz) API: some TimeZone methods can't deal with GMT offset and DST rule changes
Relates :  
JDK-5054346 - Support tzdata2004a
Relates :  
JDK-6389360 - (tz) Update the time zone data file format version to 2
Description
The getAvailableIDs(int) method should be consistent with getRawOffset() which returns the GMT offset of the time zone at the current time. Currently, getAvailableIDs(int) assumes the last known GMT offset.
###@###.### 2004-06-01
JCK test case TimeZone2014 checks consistencies between the time zone offset given to TimeZone.getAvailableIDs(int) and the retrun value of TimeZone.getRawOffset() of each time zone returned by the getAvailableIDs(int) call. TimeZone0003 could be affected if time zone's future GMT offset change is related to min or max values.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: dragon mustang FIXED IN: mustang
18-08-2004
EVALUATION getAvailableIDs(int) should assume the current time for the given GMT offset. Also getAvailableIDs(int, long) and getRawOffset(long) should be added. ###@###.### 2004-06-01 This bug report will address only the problem on producing inconsistent available ID information with the getRawOffset method. The fix involves a zoneinfo data file format change (compatible change). ###@###.### 2004-07-23 After this fix, any time zones in which their GMT offset will change in the future are no longer staticly listed by getAvailableIDs(int). For example, the America/Argentina/Mendoza time zone will change its GMT offset as of 2004-10-17 midnight (local time). America/Argentina/Mendoza will be listed as GMT-04:00 before the transition, and as GMT-03:00 after that. # Mendoza (MZ) Zone America/Argentina/Mendoza -4:35:16 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May -4:00 - ART 1930 Dec -4:00 Arg AR%sT 1969 Oct 5 -3:00 Arg AR%sT 1990 Mar 4 -4:00 - WART 1990 Oct 15 -4:00 1:00 WARST 1991 Mar 1 -4:00 - WART 1991 Oct 15 -4:00 1:00 WARST 1992 Mar 1 -4:00 - WART 1992 Oct 18 -3:00 Arg AR%sT 1999 Oct 3 -4:00 Arg AR%sT 2000 Mar 3 -3:00 - ART 2004 May 23 -4:00 - WART 2004 Oct 17 -3:00 - ART Note that America/Argentina/Mendoza is a new name of America/Mendoza in tzdata2004b. ###@###.### 2004-08-11
11-08-2004