[En-Nut-Discussion] TCP sockets stuck in closing state

[Coleman Brumley]

I haven't been able to revisit it, but it's almost as if the call to
NutTcpFindSocket isn't returning the sockets that are in the CLOSING state
which is causing them to never be serviced. 

So, I'm wondering if the assumption in calling NutTcpFindSocket in the TCP
FSM thread is that sockets won't be in the CLOSING state long enough to get
serviced. 

And, I apologize, I've been replying to Stefan directly. I will forward my
replies to the list. 

Coleman

> -----Original Message-----
> From: en-nut-discussion-bounces at egnite.de [mailto:en-nut-discussion-
> bounces at egnite.de] On Behalf Of Henrik Maier
> Sent: Wednesday, May 06, 2015 7:23 PM
> To: en-nut-discussion at egnite.de
> Subject: Re: [En-Nut-Discussion] TCP sockets stuck in closing state
> 
> Reading your post I now remember that I had a similar effect with sockets
> stuck and it was after I played with changing thread priorities which
resulted
> in starving the TCP thread. So your hint is worthwhile to follow up.
> 
> In fact I never had much luck changing Nut/OS thread priorities.
> Whenever I did that it had some side-effect, so I now always leave
> everything at default settings.
> 
> Henrik
> 
> On 7/05/2015 2:07 AM, Stefan Hax wrote:
> > It almost looks like the SM thread doesn't get to run because of a
> > busy loop somewhere.
> 
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion