[En-Nut-Discussion] TCP Socket waiting in TCPS_CLOSE_WAIT

Stephen Noftall stephenn at lcsaudio.com
Fri Mar 7 20:13:57 CET 2003


Sorry, silly me!

I found my problem, and it was to do with my two socket threads (read and
write), and how they communicate the online status between them.

Thanks again;

Stephen Noftall

----- Original Message -----
From: "Stephen Noftall" <stephenn at lcsaudio.com>
To: <en-nut-discussion at egnite.de>
Sent: Friday, March 07, 2003 9:31 AM
Subject: Re: [En-Nut-Discussion] TCP Socket waiting in TCPS_CLOSE_WAIT


> Hi Michael;
>
> > ****probably not thr best but it works
> >   while(sock->so_state != TCPS_CLOSE_WAIT)
> >   {
> >    if (ProcessMBQuery(sock) == -1)
> >     break;
> >
> >    NutThreadYield();
> >   }
> > ****
>
> This is where my problem lies. I use NutTcpSend() and NutTcpReceive(), and
> when they are recalled, they never seem to return. So in my TCP thread, I
> cannot check the socket state. I have tried to change the timeouts,
without
> any luck. They are initialized to zero, and with them at zero a socket
> connection will work and conenct. If I change the timeout to anything
under
> 20000, it seems to transmit and receive unreliably. Hmmm, more debuggery
is
> needed ;-)
>
> Cheers, and thanks for the tips!
>
> Stephen Noftall
>
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo/en-nut-discussion




More information about the En-Nut-Discussion mailing list