The 500 status is an essential issue if you want to read SOAP Faults, since they are
accompanied by a 500 status.
Prior to version 2.3, Apache SOAP provided no means for the client to specify whether
Nagling would be enabled or disabled. When the ability to specify this was added, it
was decid
Thanks a lot (and also for Scott on the suggestion on NoTcpDelay). I will
try the setNoTcpDelay first (as it's much simpler) and see if there is any
help. If situation does not improve, I will try the HTTPClient solution.
Meanwhile, I have two questions (actually for Scott):
(1) I know that the T
bk> I knew that Apache SOAP only support HTTP 1.0 and I've searched
bk> through the archive of this mailing list and don't see anyone
bk> doing HTTP 1.1. Is it very diffcult to do? We are not HTTP expert
bk> but we do want to know if it is possible to do it.
I don't know about the server side, but
Yes, Apache SOAP only does HTTP 1.0. It would be a fair amount of work to support
HTTP 1.1, because of persistent connections, but also chunking and the likes. If it
were not so much work, I would have already done it ;-). Also, I have hesitated
because so many services disable persistent con
Hi Susantha,
It's Java - the code base is Apache SOAP 2.3.1 with some minor code changes (mainly on adding some trace messages).
Billy
To: <[EMAIL PROTECTED]>
cc: Billy T S KAN/TRS IBM APH/HBAP/[EMAIL PROTECTED]
Our Ref:
Your Ref:
Subject: Re: HTTP 1.1 Pers
Hi Billy,
What is the SOAP engine you are using ? Axis ? C++ or Java ?
Thanks,
Susantha.
> Hi all,
>
> We are currently facing a performance problem in using Apache SOAP to
> sending a high volume of SOAP messages to a remote server. Our network
> people told us that one of the issue is that th
Hi all,
We are currently facing a performance problem in using Apache SOAP to
sending a high volume of SOAP messages to a remote server. Our network
people told us that one of the issue is that there is a lot of TCP
handshaking and they suggest us to use HTTP 1.1 persistent connection.
I knew tha
