🚀 go-pugleaf

It is a pointer to data in another thread that could be getting changed 
somehow.  Would have to look deeper.  I have error log loaded in the program 
and it catches exception "EInvalidPointer", but sometimes also catches 
"ESocketError - Only one usage of each socket address is normally 
permitted", but think I have handled that one now.  Good to know SendBuf 
would not be throwing the excpection, so can focus on other reasons pointer 
might be getting messed up.

I would agree with you that the socket is no longer the issue main, thanks 
for all the help.

Justin


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:44ad7444$1@newsgroups.borland.com...
>
> "Justin L Hudson" <justin.hudson@bepco.com> wrote in message
> news:44ad61ce$1@newsgroups.borland.com...
>
>> Also the clients connected have about a 5 second timer if they
>> do not get data they will close() and try and reconnect again.
>
> You should implement that scheme inside your server code as well.  If the
> server does not receive data from a client after while, then disconnect 
> the
> client.  Then make your clients send data periodically to keep the
> connection alive.
>
>> I have a try {} and catch {} around 'SendBuf', but in some rare
>> cases it will throw an "Invalid Integer" as the exception
>
> SendBuf() does not throw that exception.  You probably passed in an 
> invalid
> memory block.  What is the actual exception class type and completely
> Message?  What does your sending code look like?
>
>> Also happens with the ErrorCode being set to zero on 'OnClientError'
> event.
>
> All the more reason to suspect that the exception is occuring outside of 
> the
> socket altogether.
>
>
> Gambit
>
>