axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Perry (JIRA)" <>
Subject [jira] Commented: (AXISCPP-269) calling a service which returns a large string fails to get full message
Date Mon, 22 Nov 2004 09:29:28 GMT
     [ ]
Andrew Perry commented on AXISCPP-269:

Hi Andrew,
    You have not mentioned anything reltaed to timeout: so I guess you have not set any timeout.
    If that is the case, the problems seems to be with the transport. May be it ends reading
prematurely. The problem would also be in the deserializer, where it fails to work till it
finds the end of the string.
    I was not using -g with my client for echo sample. Hence echo works for me on Linux without
debug flag.
   If possible please send the WSDL of your service, so that I could try the same service.



There is no exception or error, the string gets returned to the client, it
is just not the correct length. It is also not consistant how many bytes
get lost and sometimes it works. Strangely it always seems to work when the
code is compiled with debugging, on Linux at least (-g flag).

Also my service is slightly different in that it does not echo a string,
but requests a string of a certain size, i.e. send an int and return a

> calling a service which returns a large string fails to get full message
> ------------------------------------------------------------------------
>          Key: AXISCPP-269
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: Transport (axis2)
>     Reporter: Andrew Perry

> One of the standard tests, LargeReturningString which sends an int to a service indicating
the size of the string to return fails to return the full string to the client. I am requesting
a 2Mb (1024*1024*2) string to be returned and the client only receives a 2089768 (this is
not consistant) byte string, as reported by strlen, rather than the expected 2097152 byte
> The service is running on IBM WebSphere which returns a chucked message in 8K chunks.
The monitor program in ws-axis/c/tests/utils/monitor captures the message on the wire and
writes it to a file, and this message is correct, so it's definitely a problem in the AxisClient

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message