[ http://nagoya.apache.org/jira/browse/XERCESC-501?page=history ]

Alberto Massari updated XERCESC-501:
------------------------------------

    Priority: Major

> Xerces hangs in ThrowXML
> ------------------------
>
>          Key: XERCESC-501
>          URL: http://nagoya.apache.org/jira/browse/XERCESC-501
>      Project: Xerces-C++
>         Type: Bug
>   Components: Utilities
>     Versions: 1.7.0
>  Environment: Operating System: Windows NT/2K
> Platform: PC
>     Reporter: Mikael Widenfalk
>     Assignee: Xerces-C Developers Mailing List

>
> I have several threads (CWinThread) that use Xerces. Sooner or later one 
> specific thread gets stuck in ThrowXML. The exact point varies depending on what 
> I send in systemID. This is one example:
> void XMLURL::setURL(const XMLCh* const    baseURL
>                   , const XMLCh* const    relativeURL)
> {
>     cleanup();
>     // Parse our URL string
>     parse(relativeURL);
>       //
>       //  If its relative and the base is non-null and non-empty, then
>       //  parse the base URL string and conglomerate them.
>       //
>       if (isRelative() && baseURL)
>       {
>               if (*baseURL)
>               {
>                       XMLURL basePart(baseURL);
>                       if (!conglomerateWithBase(basePart, false))
>                       {
>                               cleanup();
> ---->                         ThrowXML(MalformedURLException, 
> XMLExcepts::URL_RelativeBaseURL);
>                       }
>               }
>       }
> }
> [ baseURL = "Client" relativeURL = "Information-1-0.dtd" ]
> The calltree proceeds with:
> [EMAIL PROTECTED]
> KERNEL32!77e989d1()
> so there are no more clues there I guess. The CPU is at 0% and it appears as 
> though everything is stuck in some mutex.
> I've made a (large) test program that spawns 50 threads and parses 50 DTD'd XML 
> documents in each and it also occasionally gets stucks.
> Brief facts of the case are:
> * Single thread single point of initialization.
> * Uses SAX.
> * New parser, etc. for each document read.
> * Uses MemBufInputSource.
> * Uses MS VS6 sp5.
> Sorry if this provides little clue as to what goes on. Please contact me for 
> more specfic information, if needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to