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=8289>. 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=8289 transcoder map is not thread safe on SMP machines Summary: transcoder map is not thread safe on SMP machines Product: Xerces-C++ Version: 1.7.0 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Non-Validating Parser AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Firstly, this may be a "feature" and well known, and not a bug at all. However, it came as a shock to me, so I thought it useful to report. I had many (~100) DOMParser instances, each of which was accessed by its own separate thread. During a "parse" call, eventually (after about 5 minutes of continuous use of all threads running), I would start getting the exception thrown, "Could not create a converter for encoding: ..." I eventually traced this to the function "XMLPlatformUtils::fgTransService- >makeNewTranscoderFor" returning NULL. This was caused by fCPMap in Win32TransService becoming corrupted somehow! The quick fix was to place a thread-mutex (critical_section) around the "parse" function, so that no two parsers were parsing at the same time. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
