Vjacheslav Chekushin wrote: > > Ok, if we talk about not closed sockets than there is problem in http library. > > See in http.c : > /* XXX re-implement socket pools, with idle connection killing to > save sockets */ > > Every http request to new host create socket and didn't close it even > if remote side did it. > There is no any check for it. And only when gateway > will try to reuse it, socket will be closed and http will open new socket to > this host.
It does not close the socket if the client does?! *wondering* > So if system has limit for opened socket it will be exceeded sooner or later. > > Simplest solution for it - periodically check pool and destroy all > closed socket. yep, may be a solution. Anybody checked how the Apache guys do this, may be addopted. Stipe [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG M�nsterstr. 248 40470 D�sseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
