Bug ID: JDK-4388292 PST timezone now appears as GMT -08:00 on Linux 122

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

Priority: P1
Status: Closed
Resolution: Fixed
OS: linux
CPU: x86

Submitted: 2000-11-10
Updated: 2001-03-02
Resolved: 2001-03-02

Versions (Unresolved/Resolved/Fixed)

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.

Other
1.2.2_008 008Fixed

Where : Y2K testing on Linux platform. 

        Did not show on JDK122_006 on Linux but shows on JDK122_007.

How to run :  javac test_SimpleDateFormat.java
              java test_SimpleDateFormat

See Attachment for the testcase

Output
------
JDK122_007 in Solaris and Windows gives
----------------
Normal date:
Fri Mar 13 12:22:43 PST 1998
2000 date:
Tue Feb 29 13:40:22 PST 2000
1996 date:
Thu Feb 29 08:15:15 PST 1996


BUT JDK122_007 IN LINUX GIVES
------------
Normal date:
Fri Mar 13 12:22:43 GMT-08:00 1998
2000 date:
Tue Feb 29 13:40:22 GMT-08:00 2000
1996 date:
Thu Feb 29 08:15:15 GMT-08:00 1996

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: 1.2.2_008 INTEGRATED IN: 1.2.2_008 VERIFIED IN: 1.2.2_008

14-06-2004

EVALUATION I found out the problem is caused by getenv call returned NULL on linux, and it will return a valid string on Solaris. There are two possible solutions: 1. If the system has already set TZ as a environmental variable on linux as on Solaris, the problem will go away. 2. I found out the problem has been fixed on the latest ladybird workspace. (The fix is to read info from the system config clock file on linux to get the info). So the other solution is to backport the latest fix from ladybird workspace. ###@###.### 2000-11-12

12-11-2000