🚀 go-pugleaf

"Ben" <TerNOra@etraSPAMde.nl> wrote in message
news:4208d668$1@newsgroups.borland.com...

> I'm using a client socket in nonBlocking mode.
> The data handling is done in a thread to keep track of the
> not sent packages in a circular buffer and resent them on
> reconnection.

Threading works better if you use blocking mode instead.

> I try to reconnect by setting:
>     if (!TCPForm->ClientSocket->Active)
>        TCPForm->ClientSocket->Active=true;

You did not show where you are calling that from.

> but this is not working secure, it takes different times to reconnect.

Quite possibly, yes, especially since you are using non-blocking mode, so
the socket has to process a bunch of internal window messages before the
connection is fully established.

> Error message generated sometimes, say one in 10 to 20 reconnections:
> ESocketError, Windows SocketError, Illegal argument 10022 on API
> "WSACancelASyncRequent"

The only time Borland's socket components call WSACancelAsyncRequest() is
when Disconnect() is called while a lookup is still in progress from a
previous connect attempt.  Where are you calling Disconnect() from?  Most
likely, Disconnect() is being called after the lookup has actually
completed, but before the resulting window message has been processed.
Thus, component's internal lookup handle has not been nulled yet but now
points to an invalid lookup task.

> This message is received sometimes at the:
> if (ClientSocket->Active)
>    ClientSocket->Socket->SendBuf((void*)&Message,sizeof(TCPmessageType));

SendBuf() calls Disconnect() if the data fails to be sent due to a socket
error.  My guess would be that your threading code is not using the socket
property to begin with, so your code conflicts with itself at times.  Please
show your actual code.


Gambit