Bug ID: JDK-4066956 TimeZone Strings do not match Solaris TZ strings

Type: Bug
Component: core-libs
Sub-Component: java.util
Affected Version: 1.1.3

Priority: P3
Status: Closed
Resolution: Duplicate
OS: solaris_2.5.1
CPU: sparc

Submitted: 1997-07-24
Updated: 1997-10-23
Resolved: 1997-10-23


Name: rlT66838			Date: 07/23/97


The timezone string for for Central Europe in the
java.util.TimeZone class is set to ECT.  On Solaris
the timezone environment variable is set to either
CET or MET (they are the same).  If TZ is set to MET
Java translates it into Middle East Time (GMT+3.5 hours).

There needs to be some consistency between the systems
as it causes a lot of problems with client/server system
running with the server in one time zone and multiple clients
running in different time zones.
company - Sun Microsystems - UK , email - ###@###.###
======================================================================

WORK AROUND Name: rlT66838 Date: 07/23/97 I always set the sever to run with a TZ of GMT, and the clients with a valid Java timezone string. ======================================================================

11-06-2004

Duplicate :	JDK-4069784 - TimeZone.getDefault() returns incorrect time zome.
Relates :	JDK-4107380 - Calendar.getTime() returns time GMT + 3.5 hours.