JDK-4264153 : format classes are not thread-safe, and not documented as such
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.text
  • Affected Version:
    1.1.4,1.1.6,1.2.0,1.2.2,1.3.0,1.3.1,1.3.1_02,1.4.0,5.0,6 1.1.4,1.1.6,1.2.0,1.2.2,1.3.0,1.3.1,1.3.1_02,1.4.0,5.0,6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS:
    generic,solaris_2.6,solaris_7,solaris_8,solaris_9,windows_95,windows_nt,windows_2000,windows_xp generic,solaris_2.6,solaris_7,solaris_8,solaris_9,windows_95,windows_nt,windows_2000,windows_xp
  • CPU: generic,x86,sparc
  • Submitted: 1999-08-20
  • Updated: 2001-05-22
  • Resolved: 2001-05-22
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.
1.4.0 beta2Fixed
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  

Name: rlT66838			Date: 08/19/99

It has been noted in bug #4146524 that the format classes are
not thread-safe.  The wisdom of this decision aside (it's bitten
a bunch of people, myself included), I have never seen any 
mention of this fact in the documentation.  Not being thread-safe 
is a significant limitation on a class, with potentially dire 
results, and not documenting the classes as such is dangerous.
(Review ID: 94152) 

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin-beta2 FIXED IN: merlin-beta2 INTEGRATED IN: merlin-beta2

EVALUATION Planned for Merlin. norbert.lindenberg@Eng 2001-03-20 Name: nl37777 Date: 05/21/2001 The specifications of Format, MessageFormat, NumberFormat, DecimalFormat, ChoiceFormat, DateFormat, and SimpleDateFormat have been updated to document the lack of thread-safety. We looked into making the classes thread-safe instead, but they were never really designed for that, and synchronizing them and other classes involved (in particular Calendar and TimeZone) to the extent necessary would have introduced the risk of serious performance bottlenecks. ======================================================================