[Serdev] TCP problems

[Klaus Darilion]

Katty Xiong wrote:
> Hi Klaus,
> 
> I use sipp-1.1rc8. The version seems fixed the problem
> you mentioned. I didn't observe any broken SIP message
> sent by SIPp.
> 
> The problem seems: 
> With high load, one cpu @ SER is saturated, TCP @ SER
> have 0 receiver window first. When SER has 0 receiver
> window, SIPp UAC couldn’t send anything and stucks
> somewhere in the send() function, so it couldn’t
> receive anything. As a result, TCP @ SIPp has zero
> receive window finally, and TCP @ SER has zero sending
> window as a result.

Hi Katty!

Yes, I've seen this problem too. Somehow we get a deadlock. the 
application's don't read anymore as they are blocked during sending.

Not sure if the problem is in ser, sipp or in both applications - I 
could not find a solution. Maybe you have more luck.

Nevertheless it shows that an application must be programmed in a 
non-blocking way.

regards
klaus

-- 
Klaus Darilion
nic.at