Re: Problem with blocking connect().

Hi, Oded.
As I undestand from kannel architecure, we have 1 thread that write requests 
from client to network. So if one connect will blocks for 1 minute, then thread
stops to serve other requests for this time and other clients wait for
this time too.
I don't think that it is right policy.


Oded Arbel wrote:

> There's really no point in doing a non-blocking connect, as the HTTP

thread is a stand alone and 1 to 2 requests a second is not enough of a heavy load.

the connect blocks because the server isn't answering fast enough, 

and that's ok too (I mean - its ok for the client to block, 

its not ok that the server is taking its time).
> 
> --
> Oded Arbel
> m-Wise mobile solutions
> [email protected]
> 
> +972-9-9581711 (116)
> +972-67-340014
> 
> ::..
> Experience is what causes a person to make new mistakes instead of old ones.
> 
> 
> 
> 
> 
>>-----Original Message-----
>>From: Vjacheslav Chekushin [mailto:[email protected]]
>>Sent: Monday, October 21, 2002 12:45 PM
>>To: devel
>>Subject: Problem with blocking connect().
>>
>>
>>Hi, list.
>>I have problem with kannel 1.2.0.
>>In production enviroment I forced to use kannel 0.12.3.
>>If I use 1.2.0 under heavy load (realy not so 'heavy', it's about 1-2
>>request per second) then kannel periodically hangs up for some time.
>>After some investigation it seems I find where is the problem.
>>I think it is in http_start_request -> write_request -> conn_open_tcp.
>>
>>There is remark at begining of conn.c :
>>TODO: have conn_open_tcp do a non-blocking connect().
>>
>>So in my case connect blocks fairly often and kannel is
>>unusable.
>>


-- 
Vjacheslav Chekushin                                mailto:[email protected]
Latvian Mobile Phone Company                        http://www.lmt.lv