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 "fasalu rahman (JIRA)" <xe...@xml.apache.org> on 2007/12/26 16:49:43 UTC

[jira] Created: (XERCESC-1770) getting segmentation fault in xercesc_2_6::XMLReader::peekNextChar() while handling large XML list of node size of 1500,invoked by multiple client instances

getting segmentation fault in xercesc_2_6::XMLReader::peekNextChar() while handling large XML list of node size of 1500,invoked by multiple client instances
------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: XERCESC-1770
                 URL: https://issues.apache.org/jira/browse/XERCESC-1770
             Project: Xerces-C++
          Issue Type: Bug
    Affects Versions: 2.6.0
         Environment: Solaris 5.8
            Reporter: fasalu rahman


xerces 2.6 fails to handle multiple requests by simultaneous clients for large XML lists containing about 1500 nodes.
Its working fine for single client instance.The segfault happens ONLY when I've more than 2 instances/clients running simultaneously!!

The dbx trace shows the following:
------------
xercesc_2_6::XMLReader::peekNextChar
xercesc_2_6::ReaderMgr::peekNextChar
xercesc_2_6::XMLScanner::senseNextToken
xercesc_2_6::IGXMLScanner::scanNext
XMLParserXerces::next
axiscpp::SoapDeSerializer::getElement
axiscpp::SoapDeSerializer::getElementAsString
axiscpp::Call::getElementAsString
-------------

Actually I'm calling the getElementAsString method of Axiscpp inside my client application which inturn makes use of the xerces methods/libraries for parsing after getting response from the web server.
Any hints to the problem?Is there any known issues with xerces like this?
Any helps/suggestions would deeply be appreciated.
Thanks in advance,
fasal

 






-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Closed: (XERCESC-1770) getting segmentation fault in xercesc_2_6::XMLReader::peekNextChar() while handling large XML list of node size of 1500,invoked by multiple client instances

Posted by "David Bertoni (JIRA)" <xe...@xml.apache.org>.
     [ https://issues.apache.org/jira/browse/XERCESC-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Bertoni closed XERCESC-1770.
----------------------------------

    Resolution: Invalid

Please do not open bug requests to ask questions.  Instead, please subscribe and post to the Xerces-C users list:

http://xml.apache.org/mail.html#xerces-c-user

> getting segmentation fault in xercesc_2_6::XMLReader::peekNextChar() while handling large XML list of node size of 1500,invoked by multiple client instances
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: XERCESC-1770
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1770
>             Project: Xerces-C++
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>         Environment: Solaris 5.8
>            Reporter: fasalu rahman
>
> xerces 2.6 fails to handle multiple requests by simultaneous clients for large XML lists containing about 1500 nodes.
> Its working fine for single client instance.The segfault happens ONLY when I've more than 2 instances/clients running simultaneously!!
> The dbx trace shows the following:
> ------------
> xercesc_2_6::XMLReader::peekNextChar
> xercesc_2_6::ReaderMgr::peekNextChar
> xercesc_2_6::XMLScanner::senseNextToken
> xercesc_2_6::IGXMLScanner::scanNext
> XMLParserXerces::next
> axiscpp::SoapDeSerializer::getElement
> axiscpp::SoapDeSerializer::getElementAsString
> axiscpp::Call::getElementAsString
> -------------
> Actually I'm calling the getElementAsString method of Axiscpp inside my client application which inturn makes use of the xerces methods/libraries for parsing after getting response from the web server.
> Any hints to the problem?Is there any known issues with xerces like this?
> Any helps/suggestions would deeply be appreciated.
> Thanks in advance,
> fasal
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (XERCESC-1770) getting segmentation fault in xercesc_2_6::XMLReader::peekNextChar() while handling large XML list of node size of 1500,invoked by multiple client instances

Posted by "fasalu rahman (JIRA)" <xe...@xml.apache.org>.
    [ https://issues.apache.org/jira/browse/XERCESC-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554546 ] 

fasalu rahman commented on XERCESC-1770:
----------------------------------------

Thanks for the prompt response. Will post this to the Xerces-C users list.


> getting segmentation fault in xercesc_2_6::XMLReader::peekNextChar() while handling large XML list of node size of 1500,invoked by multiple client instances
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: XERCESC-1770
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1770
>             Project: Xerces-C++
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>         Environment: Solaris 5.8
>            Reporter: fasalu rahman
>
> xerces 2.6 fails to handle multiple requests by simultaneous clients for large XML lists containing about 1500 nodes.
> Its working fine for single client instance.The segfault happens ONLY when I've more than 2 instances/clients running simultaneously!!
> The dbx trace shows the following:
> ------------
> xercesc_2_6::XMLReader::peekNextChar
> xercesc_2_6::ReaderMgr::peekNextChar
> xercesc_2_6::XMLScanner::senseNextToken
> xercesc_2_6::IGXMLScanner::scanNext
> XMLParserXerces::next
> axiscpp::SoapDeSerializer::getElement
> axiscpp::SoapDeSerializer::getElementAsString
> axiscpp::Call::getElementAsString
> -------------
> Actually I'm calling the getElementAsString method of Axiscpp inside my client application which inturn makes use of the xerces methods/libraries for parsing after getting response from the web server.
> Any hints to the problem?Is there any known issues with xerces like this?
> Any helps/suggestions would deeply be appreciated.
> Thanks in advance,
> fasal
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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