The fix for bug 5088889 and escalation 1-3216881 introduces a new issue.

This issue is only reproducible with 1.3.1_xx , its fixed in 1.4.2 or 1.5.0

Attached is the simple test case.

Before running the test, change the system time settings as follows.
Change the Date to April 4, 2004 and time to 1:58:00 AM ( This is 2 min before we switched over to daylight savings time this year) Set the timezone to Pacific , but UNCHECK the "Automatically adjust clock for daylight savings changes". (as in the attached picture). This is important to reproduce the problem.

Run the attached class.
Now, let the system time change to 2:00am on April 4, then run the test class again. You will see that the system time shows 2:00am, while the test class output shows 3:00am.

It seems that if in the system time setting, you select a timezone that has the checkbox to adjust for daylight savings, the jvm does not recognize the fact that this box is unchecked. Timezones such as Arizona and Indiana which do not even display this checkbox (and do not change for daylight savings) work fine.

Now try to reproduce it with the fix for 1-3216881 . The time zone change issue is taken care off, but the test program now outputs the date in GMT (??) format instead of the correct time zone.

According to Rob Mckenna
"Hi Manish,

Development see this problem as a separate issue. As far as they are concerned this has been fixed and the difference in timezone names is another problem altogether. We need to open a separate CR to work on this issue. Please file it as soon as you get the chance. We will also need a new escalation (sorry about this) id in order to putback the fix from this new CR...

   -Rob "

###@###.### 2005-2-02 18:16:07 GMT