Hi, 2008/7/30, Tom Wieczorek <[EMAIL PROTECTED]>: > > Hi Niklas, > > only one single client is on the same box, all other clients, especially > the ones connecting to the http service, are running on different machines. > I am definitely not sure that all clients close their sockets correctly, but > this shouldn't be a problem on the server side, if the server closes the > session?
It shouldn't. If you look at the tcp state diagram*, you'll see that CLOSE_WAIT means that your application needs to send the final FIN. So it is ftpserver/mina or some issue in java tcp socket implementation itself. christian * http://www.vs.inf.ethz.ch/edu/WS0102/VS/TCP-State-Diagram.html regards, > Tom. > ----- Original Message ----- From: "Niklas Gustavsson" < > [EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, July 29, 2008 7:27 PM > Subject: Re: NioSocketAcceptor - Too many open files > > > On Tue, Jul 29, 2008 at 6:45 PM, Tom Wieczorek <[EMAIL PROTECTED]> wrote: >> >>> Hi Niklas, >>> >>> I followed the instructions found in the FAQ, although I think that this >>> is >>> not the root of the problem. The FAQ says something about TIME_WAIT, not >>> CLOSE_WAIT. I don't know if these two are the same. Another thing that >>> makes >>> me think this is not a timeout problem is the effect that the connections >>> listed in CLOSE_WAIT state remain in this state forever, not just for a >>> couple of minutes. >>> >> >> My bad, I didn't read you initial email careful enough. In your >> environment, are you client on the same box as the server? Are you >> sure that the client closes it's socket? >> >> /niklas >> >> > >
