Hi, I use the same test as I sent to the alias ealier.
SIPp UAC ---------------SER--------------SIPp UAS 199.199.2.31 199.199.2.50 199.199.2.30 Problem: SIPp UAC get broken pipe error with high load (800CPS). Traces show the cause is as follows: With high load, one cpu @ SER is saturated, TCP @ SER have 0 receiver window first. When SER has 0 receiver window, SIPp UAC couldnt send anything and stucks somewhere in the send() function, so it couldnt receive anything. As a result, TCP @ SIPp has zero receive window as a result. After this, both sides couldn't exchange any messages. After the connection is idle for some time, SER resets the connection and SIPp get "broken pipe" error. I notice SIPp actually used non-blocking send (send_nowait()), but why the nonblocking send blocks after TCP window at the other side closed? Does any one see the similar problem? The OS I am using is Solaris. thanks, Joy ____________________________________________________________________________________ Need a quick answer? Get one in minutes from people who know. Ask your question on www.Answers.yahoo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
