You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@xerces.apache.org by bu...@apache.org on 2001/09/28 15:53:44 UTC

DO NOT REPLY [Bug 3867] New: - IDOM_Element::getElementsByTagName() threading problem

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=3867>.
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=3867

IDOM_Element::getElementsByTagName() threading problem

           Summary: IDOM_Element::getElementsByTagName() threading problem
           Product: Xerces-C++
           Version: Nightly build
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: DOM
        AssignedTo: xerces-c-dev@xml.apache.org
        ReportedBy: rich.christy@citadelgroup.com


If a multi-threaded application, each with its own instance of different a 
document.  There appears to be a problem when multiple threads call 
IDOM_Element::getElementsByTagName().  My application core dumps in within a 
call to IDeepNodeListImpLLfindBucketElem().  The stack trace basically is as
follows:

getElementsByTagName()
   IDDeepNodeListImpl::getDeepNodeList()
       IDDeepNodeListImp::getByKey()
           IDDeepNodeListImp::findBucketElem()

I'm using the 9/14/01 build.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org