|
Quick Lists
|
|
Bug ID:
|
4472743
|
|
Votes
|
0
|
|
Synopsis
|
regression: EXCEPTION_ACCESS_VIOLATION in TimeZone.getSystemTimeZoneID() on W2k
|
|
Category
|
java:classes_util_i18n
|
|
Reported Against
|
merlin-beta2
|
|
Release Fixed
|
1.4(merlin-beta2)
|
|
State
|
11-Closed,
Verified,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
4152725
|
|
Submit Date
|
21-JUN-2001
|
|
Description
|
The JVM (Merlin beta-refesh b69) crashes during the start of Forte for Java 3.0 in the java.util.TimeZone.getSystemTimeZoneID call on Windows 2000 (full stack-trace attached).
After some experiments it seems that the only problematic time zone is
(GMT +1:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague
Other time zones, e.g.
(GMT +1:00) Brussels, Copenhagen, Madrid, Paris
seem to be ok.
|
|
Work Around
|
The user can set a different time zone.
--
Define "user.region" for your locale. For example,
$ java -Duser.region=JP ...
will work for Japan.
xxxxx@xxxxx 2001-06-22
|
|
Evaluation
|
Time zone detection code uses the user.region property value (not always, depending on zones where a mapID is shared). (mapID stored in Win32 "Time Zones" registries is a value to identify a location.)
The 4152725 fix changed "user.region" to "user.country". So, in the detection code, it refers to addr 0 pointed to by a null pointer.
xxxxx@xxxxx 2001-06-22
There were a number of other places where "region" hadn't been consistently been renamed to "country". These were fixed along with the regression.
xxxxx@xxxxx 2001-06-27
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
