Reserved Topics

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 use a reserved string only for the first hierarchical level of the topic subscription; others may reserve more than one level.

Solace reserves topics starting with # or _ for its own purposes. Topics defined by applications should not start with # or _, otherwise they run the risk of colliding with special topics defined in the future.

Topic Subscription Published Topics That Match the Subscription Description

#LOG/...

#LOG/level/SYSTEM/hostName/event/Name

#LOG/level/VPN/hostName/eventName/vpnName[/suffix]

#LOG/level/CLIENT/hostName/eventName/vpnName/clientName

#LOG/level/APPLICATION/hostName/eventName/vpnName[/suffix]

#LOG/INFO/SUB_ADD/subscribedTopic

#LOG/INFO/SUB_DEL/subscribedTopic

Used by the event broker to publish events to the message bus.

Published by: event broker

Subscribed to by: management client applications

#MCAST/>

#MCAST/CACHEMGR

Used by PubSub+ Cache Instances to broadcast initial messages to find their Cache Manager.

Published by: PubSub+ Cache Instances

Subscribed to by: event broker

#noexport/#share/ShareName/topicFilter

#noexport/topicFilter

topicFilter

Indicates that this subscription is not to be advertised (exported) by the local node (through MNR or DMR) to other nodes in the network.

The #noexport syntax applies only to subscriptions and is not supported for cache requests.

See Preventing Subscription Export for more information.

Published by: client applications

Subscribed to by: client applications

#P2P/CACHEINST/distributedCacheName

#P2P/CACHEINST/distributedCacheName

Used to direct PubSub+ Cache requests to a distributed cache.

Published by: client applications

Subscribed to by: PubSub+ Cache Distributed Cache

#P2P/CACHEINST/cacheClusterName

#P2P/CACHEINST/cacheClusterName

Used to direct PubSub+ Cacherequests to a cluster in a distributed cache.

Published by: client applications

Subscribed to by: PubSub+ Cache Cache Cluster

#P2P/CACHEINST/cacheInstanceName

#P2P/CACHEINST/cacheInstanceName

Used to direct PubSub+ Cache requests to a specific cache instance in a distributed cache.

Published by: client applications

Subscribed to by:PubSub+ Cache

#P2P/routerName/clientUsernameHash/#client/>

#P2P/routerName/clientUsernameHash/#client/CACHEMGR

#P2P/routerName/clientUsernameHash/#client/_CACHEMGR

Used by PubSub+ Cache Instances to communicate with their Cache Manager.

Published by:PubSub+ Cache

Subscribed to by: event broker

#P2P/routerName/#client/>

#P2P/routerName/#client/CACHEMGR

Used by PubSub+ Cache Instances to communicate with their Cache Manager.

Published by: PubSub+ Cache Instances

Subscribed to by: event broker

#P2P/v:routerName/clientUsernameHash/clientName/>

#P2P/v:routerName/clientUsernameHash/clientName/...

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

#P2P/QUE/queueName

#P2P/QUE/queueName

Used for 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

#P2P/QTMP/v:routerName/queueName

#P2P/QTMP/v:routerName/queueName

Used for 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

#P2P/TTMP/v:routerName/tempTopic

#P2P/TTMP/v:routerName/tempTopic

Used for temporary topics. The name space is controlled by the client API, but the event broker sets the prefix.

Published by: client applications

Subscribed to by: client applications

#P2P/v:routerName/>

#P2P/v:routerName/...

Used for subscriptions 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

#P2P/routerName/>

#P2P/routerName/...

Used for subscriptions 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

#SEMP/routerName/>

#SEMP/routerName/SHOW

#SEMP/routerName//ADMIN/CLIENT

#SEMP/routerName/ADMIN/DISTRIBUTED-CACHE

Used to direct SEMP commands to a physical event broker name.

Published by: client applications

Subscribed to by: event broker

#SEMP/v:routerName/>

#SEMP/v:routerName/SHOW

#SEMP/v:routerName//ADMIN/CLIENT

#SEMP/v:routerName/ADMIN/DISTRIBUTED-CACHE

Used to direct SEMP commands to a virtual router name. The subscription is present only when a given event broker is active for the virtual router name.

Published by: client applications

Subscribed to by: event broker

#share/ShareName/topicFilter

topicFilter

Used for a Direct messaging feature to load balance data among clients.

See Shared Subscriptions for more information.

A shared subscription has the form: #share/ShareName/topicFilter, where ShareName is the shared subscription identifier, and topicFilter is the topic filter.

Published by: client applications

Subscribed to by: client applications

#insights/...

#insights/pinger/ping

Used to check inter-broker connectivity by PubSub+ Cloud.

Published by: PubSub+ Insights client

Subscribed to by: PubSub+ Insights client