Home/ Questions/Q 946929
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T23:00:01+00:00

I’ve written a Delphi (2009) app with Indy (TCPServer/Client). And I have a problem

  • 0

I’ve written a Delphi (2009) app with Indy (TCPServer/Client).
And I have a problem at the level of TCPServer : it detects the deconnection(after a reboot of the PC) of the Client only when the client tries one more time to reconnect to the server.
I’ve executed my app step by step, and when the client tries top reconnect (after the reboot), the server raises (a silent, i think) exception : Connection reset by peer.
Why this exception is too late.

(I Think the thread lister is not released immediately)

What do you think ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is a low-level detail of the TCP protocol. By default, it doesn’t transmit keep-alive packets, because that wastes bandwidth, so it will only realise that the connection has died when something happens that prompts it to check the connection. (I’m not sure why a reconnection from the same client would trigger this though.)

    You can make TCP send regular keep-alive packets to discover disconnections earlier. In windows, this can be activated by the server application, but is configured via the registry (see here for details).

    You may also be able to implement a keep-alive mechanism at the protocol level by getting the client or server to send occasional null packets (a packet that does nothing in particular). This obviously requires that the protocol you are using define some kind of do-nothing or do-nothing-interesting message (NOOP, STATUS, PING … stuff like that).

    • 0