Reserved Topics
Solace PubSub+ uses a number of reserved topics to implement some specific messaging features. Each of these topic subscriptions begin with the #
character, which is then followed by a specific, reserved sequence of characters. Some special topics only use a reserved string for the first hierarchical level of the topic subscription, others may reserve more than one level.
Any topic starting with #
is reserved for special topics. Topics defined by applications must not start with #
. As an exception to this rule—with request/reply across multi-node routing networks, where a subscription propagation delay may occur—topics of the form #P2P/v:routerName/<something>
can be used.
Topic Subscription | Published Topics That Match the Subscription | Description |
---|---|---|
|
|
Used by the event broker to publish events to the message bus. Published by: event broker Subscribed to by: management client applications |
|
|
Used by PubSub+ Cache instances to broadcast initial messages to find their Cache Manager. Published by: PubSub+ Cache Instances Subscribed to by: event broker |
|
|
Any subscription (shared or non-shared) that starts with If the subscription is qualified with
Published by: client applications Subscribed to by: client applications |
|
|
Used to direct PubSub+ Cache requests to a distributed cache. Published by: client applications Subscribed to by: PubSub+ Cache Distributed Cache |
|
|
Used to direct PubSub+ Cache requests to a cluster in a distributed cache. Published by: client applications Subscribed to by: PubSub+ Cache Cache Cluster |
|
|
Used to direct PubSub+ Cache requests to a specific cache instance in a distributed cache. Published by: client applications Subscribed to by: PubSub+ Cache |
|
|
Used by PubSub+ Cache instances to communicate with their Cache Manager. Published by: PubSub+ Cache Subscribed to by: event broker |
|
|
Used by PubSub+ Cache instances to communicate with their Cache Manager. Published by: PubSub+ Cache Instances Subscribed to by: event broker |
|
|
Used for Direct Messaging request/reply. The name space is controlled by the client API, but the event broker sets the prefix. Published by: client applications Subscribed to by: client API |
|
|
Used for Direct Messaging request/reply. The name space is controlled by the client API, but the event broker sets the prefix. This pattern is used by client connections in SolOS 8.2 and below. Published by: client applications Subscribed to by: client API |
|
|
Subscriptions that allow clients to publish messages to and/or consume messages from the specified durable queues. Published by: client applications Subscribed to by: client applications |
|
|
Subscriptions that allow clients to publish messages to and/or consume messages from the specified non-durable queues. The client App/Mgmt controls the name space, but the event broker sets the prefix. Published by: client applications Subscribed to by: client applications |
|
|
Used for temporary topics. Name space is controlled by the client API, but the event broker sets the prefix. Published by: client applications Subscribed to by: client applications |
|
|
Subscription created when a virtual router is discovered, to attract #P2P traffic for the event broker. This subscription is not visible in CLI. Published by: client applications Subscribed to by: event broker |
|
|
Subscription always created when a physical event broker is discovered, to attract #P2P traffic for the event broker. This subscription is not visible in CLI. Published by: client applications Subscribed to by: event broker |
|
|
Used to direct SEMP commands to a physical event broker name. Published by: client applications Subscribed to by: event broker |
|
|
Used to direct SEMP commands to a virtual router name. Subscription is only present when a given event broker is active for the virtual router name. Published by: client applications Subscribed to by: event broker |
|
|
A Direct Messaging feature to load balance data amongst clients. A shared subscription has the form: Published by: client applications Subscribed to by: client applications |
|
|
Used to check inter-broker connectivity by PubSub+ Cloud. Published by: PubSub+ Insights client Subscribed to by: PubSub+ Insights client |