Hi Jerome, I've rebuilt using the latest from the trunk but I'm still seeing CLOSE_WAIT and FIN_WAIT_2:
127.0.0.1:3910 127.0.0.1:8002 FIN_WAIT_2 127.0.0.1:3911 127.0.0.1:8002 FIN_WAIT_2 127.0.0.1:3912 127.0.0.1:8002 FIN_WAIT_2 127.0.0.1:3913 127.0.0.1:8002 FIN_WAIT_2 127.0.0.1:3914 127.0.0.1:8002 FIN_WAIT_2 127.0.0.1:3915 127.0.0.1:8002 FIN_WAIT_2 127.0.0.1:3918 127.0.0.1:8002 FIN_WAIT_2 127.0.0.1:3919 127.0.0.1:8002 FIN_WAIT_2 127.0.0.1:3920 127.0.0.1:8002 FIN_WAIT_2 127.0.0.1:8002 127.0.0.1:3910 CLOSE_WAIT 127.0.0.1:8002 127.0.0.1:3911 CLOSE_WAIT 127.0.0.1:8002 127.0.0.1:3912 CLOSE_WAIT 127.0.0.1:8002 127.0.0.1:3913 CLOSE_WAIT 127.0.0.1:8002 127.0.0.1:3914 CLOSE_WAIT 127.0.0.1:8002 127.0.0.1:3915 CLOSE_WAIT 127.0.0.1:8002 127.0.0.1:3918 CLOSE_WAIT 127.0.0.1:8002 127.0.0.1:3919 CLOSE_WAIT 127.0.0.1:8002 127.0.0.1:3920 CLOSE_WAIT I modified the StreamServerHelper.ConnectionHandler to close sockets after it handles them and that seemed to shift a different problem to the server in that there were some TIME_WAIT sockets lingering. On Fri, Feb 15, 2008 at 8:11 AM, Kevin Conaway <[EMAIL PROTECTED]> wrote: > Hi Jerome, > > Thanks for getting back to me. I'll build from the latest trunk and let > you know. > > If the client does consume the response entity, is he still required to > release() it? > > Thanks > > > On Fri, Feb 15, 2008 at 3:14 AM, Jerome Louvel <[EMAIL PROTECTED]> > wrote: > > > > > Hi Kevin, > > > > Did you try with the very latest from SVN trunk? We have made many > > changes > > recently in this area. We are more aggressively closing connections when > > we > > know that no entity can follow the headers. > > > > However, if there is a response entity, it is the responsibility of the > > client application to consume it or to explicitly release it using the > > new > > "release()" method. > > > > Best regards, > > Jerome > > > > > -----Message d'origine----- > > > De : Kevin Conaway [mailto:[EMAIL PROTECTED] > > > Envoyé : jeudi 14 février 2008 20:59 > > > À : discuss@restlet.tigris.org > > > Objet : CLOSE_WAIT and FIN_WAIT_2 > > > > > > When using the default connectors, Restlet does not seem to > > > be properly closing connections. If I make a number of > > > requests to a resource and run netstat, I will see a number > > > of connections in the CLOSE_WAIT and FIN_WAIT_2 state. This > > > tells me that something is not getting closed properly. > > > > > > Is is the responsibility of the client to shutdown the > > > connection somehow when done? > > > > > > Kevin > > > > > > > > > > >
