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 > > À : [email protected] > > 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 > > > > > >
