axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Commented: (AXISCPP-269) calling a service which returns a large string fails to get full message
Date Fri, 19 Nov 2004 09:13:30 GMT
     [ ]
Samisa Abeysinghe commented on AXISCPP-269:

1. What is the excat error/exception that you get?
2. Do you have a timeout set in the client?

I used tests/client/performance/time test with Axis Java to send 2097152 chars. This failed
because I had a timeout set in the client.
When I disabled the timeout I could use it for 4097152 char sting without trouble.

./timeTest 4097152 http://localhost:8080/axis/services/echo

 Using service at http://localhost:8080/axis/services/echo

Time spent to invoke method ws.echoString(buffer); = 3.000000 s
User time               = 60 clock ticks
System time             = 20 clock ticks
User time of children   = 0 clock ticks
System time of children = 0 clock ticks
Processor time used     = 800000 clock ticks
Number of clock ticks per second = 100 clock ticks/s

> calling a service which returns a large string fails to get full message
> ------------------------------------------------------------------------
>          Key: AXISCPP-269
>          URL:
>      Project: Axis-C++
>         Type: Bug
>     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