Why does the Rendezvous (RV) daemon rv(r)d with clients connected to it use multiple TCP ports/sockets?

Why does the Rendezvous (RV) daemon rv(r)d with clients connected to it use multiple TCP ports/sockets?

book

Article ID: KB0085699

calendar_today

Updated On:

Products Versions
TIBCO Rendezvous -
Not Applicable -

Description

Resolution:
Environment:
===========
All


Resolution:
=========
The Rendezvous (RV) daemon rv(r)d opens a TCP client socket to establish communication between itself and RV client applications. The daemon rv(r)d -listen parameter can be used to specify the TCP port where the daemon listens for connection requests from RV clients.

Upon connection, a client application to rv(r)d initially connects on the listening port (default 7500), but then in order to free up the listen port for another application to connect to rv(r)d, the application negotiates a new port for the rv(r)d and the client application to communicate on. This new negotiated port is called an ephemeral port. On most operating systems ephemeral ports are in a range of non-privileged ports from 1024 to either 32767 or 65535 depending upon the implementation. Which ephemeral port number will be used cannot be controlled.


Keywords/Tags:
= = = = = = = = =

Issue/Introduction

Why does the Rendezvous (RV) daemon rv(r)d with clients connected to it use multiple TCP ports/sockets?