Re: closing WSP sessions

Hi Yury,

Vjacheslav Chekushin wrote:

> Hi, Yury.
> There is a problem in http.c with socket pool. Cached connection
> to http resources never cleaned from this pool, even if it closed by other
> side. So if you do not use proxy for your requests you will reach the
> limit of open descriptor soon (depend on load).
> I have patch againtst 1.3.2 which clean these connections. It doensn't
> accepted by kannel because it creates one extra thread to clean
> descriptors. But I use it in my kannel branch.

heh yes, I'm this person that don't want to have yet-another-thread if it's
avoidable with minimal costs... see patch just posted for a partial
solution.

> So either setup own proxy, either try my patch,
> either do something else (restart kannel every hour ;))
> 
> Yury Mikhienko wrote:
>> Hi developers!
>> 
>> I was start kannel wapbox on Solaris 2.9 system.
>> But after some time I got error on opening new socket to bearerbox (Too
>> many open files error) lsof command show me 277 open descriptors on
>> wapbox process, but 90% at all in CLOSE_WAIT station Can I set timeout on
>> unused WSP session and close the connect to bearerbox? Or may be closing
>> sessions (scavenging) must be automatically? I can set up system
>> parameters rlim_fd_max and rlim_fd_cur, but I do not sure of that method
>> (system overflow may be caused)
>> 
>> Thanx for your answers.
>> 
> 
> 

-- 
Thanks,
Alex