<div><br><br> </div>
<div><span class="gmail_quote">On 3/23/07, <b class="gmail_sendername">Raimo Niskanen</b> <<a href="mailto:raimo+erlang-questions@erix.ericsson.se">raimo+erlang-questions@erix.ericsson.se</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">It does not seem likely you have "a process called prim_inet:send/2".<br><br>It is also not likely it was spawned as prim_inet:send/2.
<br><br>The most likely option is that you have a process stuck in<br>prim_inet:send/2 where it has given a command to the inet driver<br>and is waiting for the response.</blockquote>
<div> </div>
<div><font color="#3333ff">>> You are exactly right. I think the exact function is gstk_port_handler:idle/1 [Surindar]</font></div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">So, is this process the only one sending replies to your clients?<br>And why does it get so many messages from other Erlang processes,
<br>and is there no flow control on those messages.<br><br>The normal way to design a server handling many clients is to<br>have one listening process and when accepting connections<br>branch them off to separate processes for each TPC connection.
<br>Then the clients can be handled in parallel within the server.<br><br>Try such a design and see if it helps.</blockquote>
<div> </div>
<div><font color="#3333ff">>>In our case too every client will communicate to the server through seperate TCP/IP communication.<font color="#3333ff">[Surindar]</font></font></div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Thu, Mar 22, 2007 at 08:17:39PM +0530, Surindar Sivanesan wrote:<br>> Dear all,<br>> We have developed a server using erlang in Windows server 2003. As many as
<br>> 200 client would be simultaneously connected to this server through TCP/IP<br>> connection. When I view the process manager table in the server, an<br>> internal process called prim_inet:send/2 is always having around 400
<br>> messages in queue. Why this process is always having messages in queue?<br>> Whether it will affect the performance of the system in any way? If so, is<br>> there any way to sort out the problem?<br>> Please give your inputs...!
<br>> --<br>> with regards,<br>> S.Surindar<br><br>> _______________________________________________<br>> erlang-questions mailing list<br>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org
</a><br>> <a href="http://www.erlang.org/mailman/listinfo/erlang-questions">http://www.erlang.org/mailman/listinfo/erlang-questions</a><br><br><br>--<br><br>/ Raimo Niskanen, Erlang/OTP, Ericsson AB<br></blockquote></div>
<br><br clear="all"><br>-- <br>with regards,<br>S.Surindar