gen_sctp full buffer lock up

Mikael Lixenstrand <>
Wed Jun 17 14:11:44 CEST 2009


Hello

I'm having problems to find who i should blame for my problems when i fill
up the buffers.

Do someone have idea if its me, otp or linux?
I use R13B.

I made a simple rewrite of the example in gen_sctp doc.

The client send messages to server with a faster speed then the server
receive to fill the buffer.
When the buffer is full the server don't get any more messages but there are
still sctp SACK received.

server_test(IP, Port, SctpTimeOut, Nr, SizeofMessage, BufferSize)

2> sctp_server:server_test({10,99,9,2}, 9090, 5, 1500, 100, 1500).
Listening on {10,99,9,2}:9090. RCV: 0 {13,2,24}
Connection Successful, Assoc={sctp_assoc_change,comm_up,0,10,10,1}
Sent: 0 {13,2,24}
RCV: 10 {13,2,24}
RCV: 20 {13,2,24}
RCV: 30 {13,2,24}
Sent: 100 {13,2,25}
Sent: 200 {13,2,26}
Sent: 300 {13,2,27}
Sent: 400 {13,2,28}
Sent: 500 {13,2,29}
SCTP RECV ERROR: timeout
Sent: 600 {13,2,30}
Sent: 700 {13,2,31}
Sent: 800 {13,2,32}
Sent: 900 {13,2,33}
SCTP RECV ERROR: timeout
Sent: 1000 {13,2,35}
Sent: 1100 {13,2,36}
Sent: 1200 {13,2,37}
Sent: 1300 {13,2,38}
Sent: 1400 {13,2,39}
SCTP RECV ERROR: timeout
okok

/
Mikael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20090617/fb52372d/attachment.html>


More information about the erlang-questions mailing list