[
https://issues.apache.org/jira/browse/AXISCPP-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548974
]
fasalu rahman commented on AXISCPP-1045:
----------------------------------------
Thanks for the response.
I tried with 1.6B version.The getElementAsString still fails,with a core in the
client.
I would like to re-define my problem for better understanding:
When i just've one client instance running even with a large XML list,
everything works fine.
But,getting a segmentation fault only when i've multiple instances,say 6.
The dbx trace points that the core happened inside the
"pReturn = m_pCall->getElementAsString ("response",0);"
I cannot blame my client/server source code/wsdl bcz its working fine in all
other cases.
Is there any known problems with the Axis/Xerces while handling multiple client
instances with large XML lists??
btw,I'm using xerces2.6 version..any hints to the reason for this problem?
Thanks in advance,
Fasal
> getting segmentation fault in the
> axiscpp::SoapDeSerializer::getElementAsString while running multiple client
> instances to access large XML list about 1500 nodes returned from server
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXISCPP-1045
> URL: https://issues.apache.org/jira/browse/AXISCPP-1045
> Project: Axis-C++
> Issue Type: Bug
> Components: Client - Deserialization, Parser Library - Xerces
> Affects Versions: 1.4 Final
> Environment: SunOS(Solaris)
> Reporter: fasalu rahman
>
> The getElementAsString method fails to handle large XML lists when invoked by
> multiple client instances
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
