-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 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
-
Component/s: core-libs
-
beta2
-
generic, x86, sparc
-
generic, solaris_2.6, solaris_7, solaris_8, solaris_9, windows_95, windows_nt, windows_2000, windows_xp
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)
======================================================================
- duplicates
-
JDK-4093418 DateFormat is not threadsafe
-
- Closed
-
-
JDK-4228335 SimpleDateFormat is not threadsafe (one more try)
-
- Closed
-
-
JDK-4411640 NumberFormat.parse() is not thread-safe
-
- Closed
-
-
JDK-4449148 [Fmt-Nu] DecimalFormat.parse is not thread-safe
-
- Closed
-
-
JDK-6609686 [Fmt-Da] Under heavy load, DateFormat format throws ArrayIndexOutOfBoundsException
-
- Closed
-
-
JDK-6609721 [Fmt-Da] java.text.SimpleDateFormat.format result some time not correct
-
- Closed
-
-
JDK-6610730 [Fmt-Da] java.text.SimpleDateFormat.parse method does not works thread safe
-
- Closed
-
-
JDK-2163870 [Fmt-Nu] DecimalFormat.parse is not thread-safe
-
- Closed
-