> Is there any kind of limitation in the response size?
There should be no defined size limit. I just tried a SOAP request with 1000 results per page, got back a complete 1.9MB xml doc.
The only standard potential limit is a search timeout, but a) it shouldn't happen with simple queries, and b) If there was a timeout, you'd get back a complete XML document with a message explaining a timeout was reached.
> in addition it happens only on linux server,
> the same request on a windows server works!
Is there any sort of error or warning conditions presented in the linux environment? On the appliance, you can also examine "vortex.log" in the "Manage Logs" section under "Appliance" right after doing a linux request to see if any information was logged on the server side.
==> vortex.log <==
006 2010-11-18 14:20:06 /ThunderstoneSearchService: (31347) Stdout error via web server to xxx.xxx.xxx.xxx: Connection reset/closed?; exiting
> ThunderstoneSearchService: (31347) Stdout error via web
> server to xxx.xxx.xxx.xxx: Connection reset/closed?;
> exiting
That tells us that the appliance saw the client close the connection unexpectedly. That, combined with the fact that it works from a Windows machine, leads me to think something wacky is going on with the axis2 client in Linux.
Unfortunately I'm not sure what it is that's causing the client to do this. Searching around turns up some tools that can help get more info, such as turning on HTTP Logging for the axis client. http://blogs.cocoondev.org/dims/archives/004668.html
We finally found a configuration that send us the whole reponse but now we've got the same message than before at the end of the response (ie 006 2010-11-18 14:20:06 /ThunderstoneSearchService: (31347) Stdout error via web server to xxx.xxx.xxx.xxx: Connection reset/closed?; exiting)
So the response is not a soap response because of that line.
> We finally found a configuration
> that send us the whole reponse
What was changed?
> now we've got the same message than before
> at the end of the response
> So the response is not a soap response
> because of that line.
That message is being printed in the response itself? That would be odd, as the message is generated due to communication with the client stopping - it wouldn't be made unless the appliance CAN'T send anything else to the client.
Would it be possible to grab a .pcap dump of the network traffic for the linux & windows server, so they can be compared & contrasted?
> another question are the binary compliant with 64bits
What binaries? The SOAP API can be used by a 64bit client, as the XML going back & forth isn't affected by it.