[OpenSIPS-Devel] SF.net SVN: opensips:[6561] trunk/tcp_main.c

Bogdan-Andrei Iancu bogdan at voice-system.ro
Wed Feb 3 11:34:33 CET 2010


Revision: 6561
          http://opensips.svn.sourceforge.net/opensips/?rev=6561&view=rev
Author:   bogdan_iancu
Date:     2010-02-03 10:34:33 +0000 (Wed, 03 Feb 2010)

Log Message:
-----------
History behind this change (WARN -> INFO):
The messages you are seeing means that the TCP MANAGER process sees that all the TCP WORKER processes are already processing other messages, so  no one is free (idle), so , it will queue the current active connection to one of the TCP WORKERs...
There is nothing wrong with this, it is the normal way it works - of course, if you have too few TCP workers, the probability to have queuing is higher.

In UDP the queueing is not visible at application level as it is done by the kernel in the receive buffer that is assigned to the socket.

In TCP the queueing is visible as there is a single TCP MANAGER process managing the connections (detecting the reads, connects, etc) which is quite fast (not doing any processing) -> the queueing is moved between the TCP MANAGER and TCP WORKERS.

Also, to be sure you got it right, there is no relation between the TCP WORKER and a connection. A TCP WORKER process is just reading and processing a SIP message at a certain time. Next SIP message from the same connection may end up in a different TCP WORKER proc.

Modified Paths:
--------------
    trunk/tcp_main.c


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.



More information about the Devel mailing list