JDK-4158102 : Solaris: TimeZone misinterprets zone id MET as "Iran Standard Time"
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 1.1.6,1.2.0
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_2.5.1
  • CPU: sparc
  • Submitted: 1998-07-16
  • Updated: 1999-08-12
  • Resolved: 1999-08-12
Related Reports
Duplicate :  
JDK-4059431 - Problem with the SystemTime on a Solaris Machine (Timezone = "WET")
Duplicate :  
JDK-4210530 - Date.toString() gives incorrect, GMT time
Relates :  
JDK-4208984 - Win32: Wrong default timezone in Melbourne Australia
Relates :  
JDK-4212004 - TimeZone.getDefault() fails for EST time zone in Australia
Description

Name: rm29839			Date: 07/16/98


This bug was previously reported and closed as bug
4037093.  It was closed as a duplicate of bugs
4069784 and 4059431 but should this is *wrong*.

See my comments at the end of 4037093, but briefly:
This bug does NOT relate to the well know default
time zone problem of Java.  Instead, this bug is simply that 
the TimeZone.java source interprets the zone id
"MET" to be "Iran Standard Time" or "Asia/Tehran"
whereas Solaris uses "MET" to mean 
"Middle Europe Time".   Please take a closer look
at this bug.  Thanks!
(Review ID: 35210)
======================================================================
Comments
WORK AROUND Name: rm29839 Date: 07/16/98 The workaround that I use is to run the JVM with France timezone but its a hassle: $ java -Duser.timezone=ECT class ======================================================================
11-06-2004
EVALUATION It has been our policy to retain the original meaning of the 3-letter time zone IDs. In a sense, the interpretation of any 3-letter zone ID is arbitrary: EST means Eastern Standard Time, but there are several ESTs in the world (US, Australia, Brazil (I think), etc.). Rather than fix the 3-letter zones, we've left them as-is -- for backward compatibility -- and added the longer Unix-style IDs, e.g., America/New_York. Given that, it doesn't seem that we should change MET, unless there is a specific, compelling reason to break existing code which uses MET to mean "Middle Eastern Time". alan.liu@eng 1998-08-12 It's wrong assumption that Solaris timezone IDs are identical to Java timezone IDs, especially three letter ones. This should be fixed. masayoshi.okutsu@Eng 1999-06-12 Fixed as 4059431. masayoshi.okutsu@Eng 1999-08-12
12-06-1999