RTT server cannot survive TCP Close

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • RTT server cannot survive TCP Close

      Hello,

      Upon ESTABLISHING the first connection to 19021, the RTT server spawns another LISTENER for 19021:

      First RTT Client wrote:

      C:\cmder
      λ netstat -aon -p tcp | findstr 19021
      TCP 127.0.0.1:19021 0.0.0.0:0 LISTENING 1268

      C:\cmder
      λ netstat -aon -p tcp | findstr 19021
      TCP 127.0.0.1:19021 0.0.0.0:0 LISTENING 1268
      TCP 127.0.0.1:19021 127.0.0.1:63311 ESTABLISHED 1268
      TCP 127.0.0.1:63311 127.0.0.1:19021 ESTABLISHED 10900
      Connecting to that LISTENER can occur. A new LISTENER is spawned, but it cannot be connected. There appears to be no functionality for these additional LISTENERS as far as I can tell.

      Disconnecting the First RTT Connection, the first client, results in:

      Disconnected First RTT Client wrote:

      C:\cmder
      λ netstat -aon -p tcp | findstr 19021
      TCP 127.0.0.1:19021 0.0.0.0:0 LISTENING 1268
      TCP 127.0.0.1:19021 127.0.0.1:63311 CLOSE_WAIT 1268
      TCP 127.0.0.1:63311 127.0.0.1:19021 FIN_WAIT_2 10900

      A new connection attempt (3rd or greater) fails to connect:

      3rd or beyond RTT Client Attempt wrote:

      C:\cmder
      λ netstat -aon -p tcp | findstr 19021
      TCP 127.0.0.1:19021 0.0.0.0:0 LISTENING 1268
      TCP 127.0.0.1:53219 127.0.0.1:19021 SYN_SENT 10900
      TCP 127.0.0.1:53245 127.0.0.1:19021 SYN_SENT 10900

      Is it possible to close and re-open the TCP connection without restarting the RTT server processes (JLink, JLinkGDB, and so on)?

      What are the additional LISTENERS for?

      Cheers,
      Joe