Hi Shankar,
I am using AXIS2/C 1.6 release.
I only specified "--prefix" option for the configure command when building 
AXIS2C, the others are default values. I guess the default for 
--enable-guththila is yes and --enable-libxml2 is no.
However, before I build AXIS2C, I set the PKG_CONFIG_PATH environment variable 
to where the pkgconfig of the libxml resides. So I am not sure if I am using 
libxml2 or guththila.

I used a firewall tool to capture the traffic from server and I did see server 
sends all the data. So I believe it is the problem in the client side.

Thanks,
Jan-fon


-----Original Message-----
From: Selvaratnam Uthaiyashankar [mailto:[email protected]]
Sent: Tuesday, February 23, 2010 10:28 PM
To: Apache AXIS C User List
Cc: [email protected]; [email protected]
Subject: Re: Client to receive large data problem

Hi,

What version of Axis2/C you are using? Are you using libxml2 or guththila?

Can you verify whether it is a network related issue? You can capture
the message and see whether server sends all the messages, and the
problem is in client side.

Regards,
Shankar

On Wed, Feb 24, 2010 at 11:32 AM, Fan, Jan-fon <[email protected]> wrote:
> Hi,
>
> Does anyone have experience in develop an application using AXIS2C client
> API to consume a web services which returns large amount of data (about 2M).
>
>
>
> When my client application receives such large data, the data will be
> truncated. This problem will get better (but not completely resolved) if I
> add 3 seconds sleep time in axis2_http_client_recieve_header() function in
> the http_client.c. I am hoping by doing so, my application can receive all
> the data before start to process the data. But this does not resolve the
> problem completely, I am wondering if there is any other solution.
>
>
>
> Thanks,
>
> Jan-fon
>
>



--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to