Steve, Every socket connection you close goes into a close wait state. The operating system is keeping those closed sockets around just in case the connection gets reused. you can set your close wait timeout to whatever you like, I recommend about 3 seconds, it of course is different depending on which os you are on. On some OSs like AIX the default is huge, even Solaris is pretty long. Linux is probably, by default, shorter. It is a standard tunable on most web server install docs. Good Luck, John
On Fri, 2006-03-31 at 10:26 -0500, Steve Terrell wrote: > My httpclient-based application is leaving connections in a CLOSE_WAIT > state. I am running HttpClient 3.0, using a single instance of > HttpClient and MultiThreadedConnectionManager. Each request created its > own HttpState and PostMethod objects, which are used to call a Tomcat > servlet. > > > > >From what I have read, I can force connections to close through various > methods. However, are sockets in a CLOSE_WAIT state really harmful? > > > > Steve Terrell > > GuideWorks, LLC, Radnor > > 610.535.4332 (v) > > 610.304.3610 (c) > > 150 N. Radnor-Chester Road Suite 300C Radnor, PA 19087 > >
