[ 
https://issues.apache.org/jira/browse/AXISCPP-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553254
 ] 

fasalu rahman commented on AXISCPP-1045:
----------------------------------------

Sorry for the delay,was busy with some other tasks.
I can't attach the wsdl/soap messages due to security reasons in my company.

Meanwhile i noted that , the xml is getting corrupted on-the-fly somewhere 
inside getElementAsString.
----------------
eg.
Actual response from Web Server:        <NAME>FOO</NAME>
Response from getElementAsString:   <NAME>FOO</NA>
----------------
Do u know any issues/fixes for this problem?
I understand that it would be difficult for you to come to a conclusion without 
the necessary wsdl/soap responses,deeply regret for the same.
As I mentioned earlier i tried with the 1.6B version and the problem persists.
Do u know any cases where the xerces fail to handle simultaneous requests with 
huge xml? 
I was using xerces2.6.Any suggestions would deeply be appreciated.
Thanks




> 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]

Reply via email to