Thank you very much for the pointer. Can I get a little more insight into a. making axis client use the CommonsHTTPSender instead of HTTPSender as the transport implementation.
b. setting properties for pooled connections/socket. Once again, thank you very much for the help. -Mahesh On 1/5/06, Jarmo Doc <[EMAIL PROTECTED]> wrote: > Last time I investigated this (with Axis 1.2), I came to the conclusion that > you need to use the org.apache.axis.transport.http.CommonsHTTPSender class > in conjunction with the Jakarta Commons HttpClient package. > > See http://issues.apache.org/bugzilla/show_bug.cgi?id=16522 > > > >From: Mahesh Seshan <[EMAIL PROTECTED]> > >Reply-To: [email protected] > >To: [email protected] > >Subject: Client drops connection > >Date: Wed, 4 Jan 2006 19:32:06 -0500 > > > >Hello, > > > >I have an Axis 1.3 (java) based Service that is consumed by an Axis > >1.3 (java) client. I notice that (netsta -a) after the client invokes > >a method, it drops the TCP connection to the server. I say this > >because, the socket on the server side changes to TIME_WAIT state > >instead of ESTABLISHED state. I am positive that on the client, I > >don't lose reference to the ServiceLocator or the Stub. Can you please > >explain me this behavior and how i can keep the connection open for > >the entire session. > > > >-Mahesh > > _________________________________________________________________ > FREE pop-up blocking with the new MSN Toolbar – get it now! > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ > >
