got around this problem by chucking my SAAJ client code and using
Axis's JAX-RPC DII interfaces instead. By creating my own Call object,
I found I could keep a socket open to the webserver I am polling.
noky
Mike Charnoky wrote:
Now that I fixed the SOAPAction bug in CommonsHTTPSender, I find
Hi, I am using Axis 1.2 (final) with the Commons HTTPClient 3.0rc2. I
am using these libraries to create a SOAP client using the SAAJ API. My
client connects to a .net webservice. It must query for data several
times per minute, so I am trying to get HTTP/1.1 keepalive support working.
I think
Now that I fixed the SOAPAction bug in CommonsHTTPSender, I find that
the TCP socket used by my client is not actually reused. Every time I
try to reuse a SOAPConnection to make a SOAPConnection.call(), a new TCP
socket is established with the server. Is this correct behavior? Isn't
the socket
