JDK-6271513 : (tz) TimeZone.getDisplayName should use ConcurrentMap for caching display names
- Type: Bug
- Component: core-libs
- Sub-Component: java.util:i18n
- Affected Version: 1.4.2,5.0
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-05-17
- Updated: 2013-11-01
- Resolved: 2005-11-21
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.
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 | JDK 6 |
|---|---|
| 5.0u7Fixed | 6 rcFixed  |
Related Reports
|
Relates :
|
Description
Date.toString was improved by eliminating static GregorianCalendar and SimpleDateFormat instances. However, it calls TimeZone.getDisplayName to get an abbreviation of a time zone. In the getDisplayName implementation, it uses a HashMap with synchronization. The HashMap should be replaced with a ConcurrentHashMap to improve concurrency. ###@###.### 2005-05-17 10:37:45 GMT
Comments
|