Special Solace Topics

The Solace messaging platform uses some reserved topics to implement some specific messaging features. Each of these special 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.

Solace Special Topic Subscriptions

.
Subscription Subscriber Published Topics Matching the Subscription Publisher Description
#LOG/... management client applications#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
routerUsed by the router to publish events to the message bus.
#MCAST/> router #MCAST/CACHEMGR SolCache Used by SolCache instances to broadcast initial messages to find their Cache Manager.
#P2P/CACHEINST/distibutedCacheName SolCache #P2P/CACHEINST/distibutedCacheName client applications Used to direct SolCache requests to a distributed cache.
#P2P/CACHEINST/cacheClusterName SolCache #P2P/CACHEINST/cacheClusterName client applications Used to direct SolCache requests to a cluster in a distributed cache.
#P2P/CACHEINST/cacheInstanceName SolCache #P2P/CACHEINST/cacheInstanceName client applications Used to direct SolCache requests to a specific cache instance in a distributed cache.
#P2P/routerName/#client/> router #P2P/routerName/#client/CACHEMGR SolCache Used by SolCache instances to communicate with their Cache Manager.
#P2P/v:routerName/clientName/> client API #P2P/v:routerName/clientName/... client applications Used for Direct Messaging request/reply.   Name space is controlled by the client API, but router sets the prefix
#P2P/QUE/queueName client applications #P2P/QUE/queueName client applications Used for durable queues.
#P2P/QTMP/v:routerName/queueName client applications #P2P/QTMP/v:routerName/queueName client applications Used for non-durable queues.  Name space is controlled by the client App/Mgmt, but router sets the prefix.
#P2P/TTMP/v:routerName/tempTopic client applications #P2P/TTMP/v:routerName/tempTopic client applications Used for temporary topics.  Name space is controlled by the client API, but router sets the prefix.
#P2P/v:routerName/> router #P2P/v:routerName/... client applications Subscription created when a virtual router is discovered, to attract #P2P traffic for the router.  Created “under the hood”, not visible in CLI.
#P2P/routerName/> router #P2P/routerName/... client applications Subscription always injected into TRB when a physical router is discovered, to attract #P2P traffic  for the router.  Created “under the hood”, not visible in CLI.
#SEMP/routerName/> router #SEMP/routerName/SHOW
#SEMP/routerName//ADMIN/CLIENT
#SEMP/routerName/ADMIN/DISTRIBUTED-CACHE
client applications Used to direct SEMP commands to a physical router name.
#SEMP/v:routerName/> router #SEMP/v:routerName/SHOW #SEMP/v:routerName//ADMIN/CLIENT
#SEMP/v:routerName/ADMIN/DISTRIBUTED-CACHE
client applications Used to direct SEMP commands to a virtual router name. Subscription is only present when a given router is active for the virtual router name.