🚀 go-pugleaf

I've got an app that maintains several different 
socket connections to multiple computers.  Most of 
the connections work fine, but one has been giving 
lots of problems lately.

The ones that work have data flowing fairly 
consistently, say a minimum of 3-5 packets in a 5 
minute period, but can be much more than that. 
The connection that gives me the problem is one 
that has periods where nothing is sent/receive for 
more than 20 minutes. The socket is still 
connected (no disconnect events or errors), but 
later on we find that the other side tried to send 
something that wasn't received by our app.  What's 
more, closing and reopening the socket doesn't 
appear to reestablish data passage, even though we 
get the connect event. It typically takes an app 
restart and/or reboot to get data passing 
(customer doesn't know difference).

Are there lower level timeouts that are occuring 
that I'm not aware of? Should there be a "keep 
alive" transmission every so often? Is something 
else happening here?

Tech info:
BCB5 using borland's TServerSocket & TClientSocket 
in asynchronous mode. The failing connection is a 
server socket running on XP pro.

I don't know if it makes any difference but more 
info is better than none. This particular 
computer/app is maintaining connections to 6 
computers simultaneously and there are two 
connections to one of them (server socket and 
client socket). The server socket that is failing 
is the one to the system that has two connections.

Thanks,
Marty