Kbase 19648: SonicMQ: Socket Connections Needed to Subscribe to a Topic
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/14/2000 |
|
SUMMARY:
Discussion of the number of socket connections needed by each subscriber to a particular topic.
EXPLANATION:
A separate client socket connection to each topic is not necessary. In the Java Messenger Service (JMS) world, a connection is a "heavyweight" object. As implemented in Progress SonicMQ, the JMS specification allows clients to create as few connection objects as possible and to instead create lighter weight session objects as needed.
Multiple sessions may be created from a single connection object.
Multiple publisher/subscriber objects (multiple sender/receiver objects for PTP) can be created from each Session object.
On the broker side, implementation of the SonicMQ JMS creates a single listener thread for each physical client connection. There is one and only one physical connection from the client to the Broker for each client process.
JMS Connections (created by the client) are multiplexed across the one physical connection. As a result, socket and thread counts are quite low. No socket or thread is created on a per-topic basis.