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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED everconfirmed|0 |1 ------- Additional Comments From [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
