[En-Nut-Discussion] TCP stops working after some time

[Jean Pierre Gauthier]

TCP runs here without locks during weeks.
Try to:
1) observe TCP sockets list (with httpserv "socket list" utility). It can
give you some ideas. 
) set timeouts with NutTcpSetSockOpt /SO_SNDTIMEO, /SO_RCVTIME ???
2) do not play with your appli priorities. Keep default value(64). (in my
application, Bugs both on TCP and usart lock when priority is modified). 
3)verify heap level. 


-----Message d'origine-----
De : en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] De la part de Bernd Walter
Envoyé : samedi 27 novembre 2004 22:55
À : en-nut-discussion at egnite.de
Objet : [En-Nut-Discussion] TCP stops working after some time

I have an application using 3.9-1 that does a lot of connects and
disconnects.
After some time the Boards doesn't respond to TCP Packets anymore, but I can
still ping it.

To me it looks very much like the tcpsm thread is lost somehow.
Will add code to output the thread list on an LCD - right now it is http
only and since TCP doesn't work in that case...

While searching inside Ethernut code I failed to see how all the
NutEventPostAsync() calls inside the TCP code are protected from interrupts.

-- 
B.Walter                   BWCT                http://www.bwct.de
bernd at bwct.de                                  info at bwct.de

_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion