Ralf,
I have experience sending longer arrays than what you are sending, but only
with SOAP 2.1 and 2.2. I have not seen the error you are seeing.
If you are concerned about the performance sending large payloads from the
client, I highly recommend you move to SOAP 2.2. That version provides a
method SOAPHTTPConnection#setOutputBufferSize that allows you to set the
output buffer size, rather than accepting the default 512 bytes. For
messages larger than 4k, setting this to 4096 will yield significant
performance improvements. The round-trip time in my tests decreased by a
factor of 5 (15 second round trip reduced to 3 seconds), although, as
always, your results may vary.
Scott
----- Original Message -----
From: "Ralf Bierig" <[EMAIL PROTECTED]>
To: "SOAP Mailing List SOAP Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 26, 2001 10:41 AM
Subject: Problems with sending long arrays via SOAP! HELP!
> Hi,
>
> I running a benchmark test with Apache SOAP 2.0.
>
> I do the following thing: I send to one service an
> array of byte value. The service just sending this
> back to the client: A simple Echo Service.
> To see, how SOAP works with high data volume, I
> increase this array continuously. When I reach a
> array-length of about 24170 byte values, I get the
> following error message:
>
> socket closed (code=0)
>
> Does somebody know, what this means?
> What can I do to avoid this?
> How can I transfer longer arrays as 24170?
> Is this a possible bug in version 2.0 of Apache SOAP?
> Solutions?
>
> Thanks in advance!
>
> Ralf
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail
> http://personal.mail.yahoo.com/
