Kbase P134766: Do all SonicMQ client connections use the same TCP broker acceptor port?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/02/2009 |
|
Status: Unverified
GOAL:
Do all SonicMQ client connections use the same TCP broker acceptor port?
GOAL:
Does the SonicMQ broker spawn processes in the background in order to spread the load for multiple connections?
GOAL:
Does SonicMQ specify a range of ports for client connections?
FACT(s) (Environment):
SonicMQ
All Supported Operating Systems
FIX:
The answer to this depends on the machine O.S. and environment. SonicMQ opens an accepting socket on the configured port for each acceptor by performing the equivalent of a Socket listen.
When a client connects, the equivalent of an accept Sockets call is performed. The exact behavior of port allocation is OS/JVM/IP Stack dependent, but typically a new local port will be allocated. So it is possible that only the port that the acceptor is configured with may be used, or alternatively several ports could be opened for each individual client connection. But as stated above, this is Stack dependent.
SonicMQ in general does not restrict the number of client connections (short of the Remote edition, but that is done be licensing, not configuration of available ports).