Thats right Deepal.. I am on Windows.. And the CLOSE_WAIT remains until i
bounce the server. But Apart from Windows, I also have a Solaris OS and the
CLOSE_WAIT remains on Solaris too until the server is bounced...


Regards,
Nirav


On Thu, Jan 28, 2010 at 10:03 PM, Deepal Jayasinghe <dee...@opensource.lk>wrote:

> Are you on Windows ? If so this is a common problem, in Windows it takes
> a while to actually close the connection.
>
> > Thanks Deepal..
> >
> > Even after doing the cleanup's. I still see the CLOSE_WAIT appears.
> > Axis2 Client makes a call to Axis 1.4 service and i get a response
> > from the service. After 30 seconds, i see a CLOSE_WAIT. If i make 2
> >  concurrent requests, i see 2 CLOSE_WAIT (netstat -a | grep
> > CLOSE_WAIT) and this remains until i bounce the server...
> >
> > Any other reason why i would  see a CLOSE_WAIT ?
> >
> >
> > Thanks,
> > Nirav
> >
> >
> >
> >
> > On Wed, Jan 27, 2010 at 8:19 AM, Deepal Jayasinghe
> > <dee...@opensource.lk <mailto:dee...@opensource.lk>> wrote:
> >
> >     try calling this;
> >
> >     client.cleanup();
> >      client.cleanupTransport();
> >
> >     Nirav Shah wrote:
> >     > Deepal.. Is the issue in the URL that something you are aware of?
> >     >
> >     >
> >     > Regrds,
> >     > Nirav
> >     >
> >     > On Tue, Jan 26, 2010 at 12:15 PM, Nirav Shah
> >     <snirav.s...@gmail.com <mailto:snirav.s...@gmail.com>
> >     > <mailto:snirav.s...@gmail.com <mailto:snirav.s...@gmail.com>>>
> >     wrote:
> >     >
> >     >     Thanks Deepal, very much appreciate a response..I have added
> the
> >     >     serviceClient cleanupTransport( ) after each service call
> >     based on
> >     >     your response below. However, i have seen a couple of folks
> >     having
> >     >     a NullPointer thrown all of a sudden when they do that in
> >     the Axis
> >     >     2.1.5.1 codebase.
> >     >
> >     >
> >     >
> >
> http://mail-archives.apache.org/mod_mbox/ws-axis-user/200911.mbox/%3cf794cee42816844aa0ffafacc80f229127e5941...@rrc-dte-exmb2.dte.telcordia.com%3e
> >     >
> >     >
> >     *http://osdir.com/ml/axis-user-ws.apache.org/2009-11/msg00230.html*
> >     >
> >     >
> >     >     Are you aware of these issue?
> >     >
> >     >
> >     >     Regards,
> >     >     Nirav
> >     >
> >     >
> >     >
> >     >
> >     >     On Tue, Jan 26, 2010 at 7:58 AM, Deepal jayasinghe
> >     >     <deep...@gmail.com <mailto:deep...@gmail.com>
> >     <mailto:deep...@gmail.com <mailto:deep...@gmail.com>>> wrote:
> >     >
> >     >         Nirav,
> >     >         Yes, try to call clean up after each request call.
> >     >
> >     >         Thanks,
> >     >         Deepal
> >     >         > Hi Thilina/Glen,
> >     >         > Can you  advice??
> >     >         >
> >     >         > I am using Axis 2.1.5.1... I do a
> >     >         >
> >     >
> >     soapBinding._getServiceClient().getOptions().setTimeOutinMillis()
> >     >         for
> >     >         > every call made to another webservice. Do i need to
> >     cleanup
> >     >         transport
> >     >         > after every call or does the AXIS2-2883 fix  cleans up
> >     after
> >     >         every
> >     >         > request. Is these issue also fixed for https ??
> >     >         >
> >     >         >
> >     >         > Regards,
> >     >         > Nirav
> >     >         >
> >     >         >
> >     >         >
> >     >         > On Mon, Jan 25, 2010 at 8:01 AM, Nirav Shah
> >     >         <snirav.s...@gmail.com <mailto:snirav.s...@gmail.com>
> >     <mailto:snirav.s...@gmail.com <mailto:snirav.s...@gmail.com>>
> >     >         > <mailto:snirav.s...@gmail.com
> >     <mailto:snirav.s...@gmail.com>
> >     >         <mailto:snirav.s...@gmail.com
> >     <mailto:snirav.s...@gmail.com>>>> wrote:
> >     >         >
> >     >         >     Anyone??Would appreciate valuable suggestions..
> >     >         >
> >     >         >
> >     >         >
> >     >         >
> >     >         >     On Sat, Jan 23, 2010 at 12:35 PM, Nirav Shah
> >     >         >     <snirav.s...@gmail.com
> >     <mailto:snirav.s...@gmail.com> <mailto:snirav.s...@gmail.com
> >     <mailto:snirav.s...@gmail.com>>
> >     >         <mailto:snirav.s...@gmail.com
> >     <mailto:snirav.s...@gmail.com> <mailto:snirav.s...@gmail.com
> >     <mailto:snirav.s...@gmail.com>>>>
> >     >         wrote:
> >     >         >
> >     >         >         Hi,
> >     >         >         I have been reading some different sides of this
> >     >         defect. Based
> >     >         >         on the Release Email sent out, it said the
> >     >         Connections are
> >     >         >         released automatically and should not need either
> >     >         >         AUTO_RELEASE_CONNECTION or *the
> >     >         >         *MultithreadedHttpConnectionManager. But the
> >     defect
> >     >         had a
> >     >         >         comment saying either the
> >     >         >         options.setCallTransportCleanup(true) is needed
> or
> >     >         after the
> >     >         >         call client.transportCleanup() is needed. Is the
> >     >         clean up
> >     >         >         still needed ? Can anyone please suggest ? AND
> >     and i
> >     >         use https
> >     >         >         , is these issue resolved for https as well ?
> >     >         >
> >     >         >
> >     >         >         Thanks,
> >     >         >         Nirav S
> >     >         >
> >     >         >
> >     >         >
> >     >
> >     >
> >     >         --
> >     >         Thank you!
> >     >
> >     >
> >     >         http://blogs.deepal.org
> >     >         http://deepal.org
> >     >
> >     >
> >     >
> >
> >     --
> >     Thank you!
> >
> >
> >     http://blogs.deepal.org
> >     http://deepal.org
> >
> >
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
> http://deepal.org
>
>

Reply via email to