commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26827] - DateLocaleConverter is not thread-safe
Date Wed, 11 Feb 2004 22:38:18 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26827>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26827

DateLocaleConverter is not thread-safe

rdonkin@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
      everconfirmed|0                           |1



------- Additional Comments From rdonkin@apache.org  2004-02-11 22:38 -------
ok. 

so it's the use of SimpleDateFormat that's problematic in a multithreaded environment that's
the issue.

what's interesting is that the syncronization requirement only appears after java 1.2. i'm
not sure 
whether the 1.4.1 class is now not guaranteed to be threadsafe or whether it's always been
that way 
(but never been documented, i'm not sure).

i'll add some synchronization some time soonish.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message