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

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 router to publish events to the message bus. 
Published by: router
Subscribed to by: management client applications
#MCAST/> #MCAST/CACHEMGR Used by SolCache instances to broadcast initial messages to find their Cache Manager.
Published by: SolCache Instances
Subscribed to by: router
#P2P/CACHEINST/distibutedCacheName
#P2P/CACHEINST/distibutedCacheName Used to direct SolCache requests to a distributed cache.
Published by: client applications
Subscribed to by: SolCache Distributed Cache
#P2P/CACHEINST/cacheClusterName #P2P/CACHEINST/cacheClusterName Used to direct SolCache requests to a cluster in a distributed cache.
Published by: client applications
Subscribed to by: SolCache Cache Cluster
#P2P/CACHEINST/cacheInstanceName
#P2P/CACHEINST/cacheInstanceName Used to direct SolCache requests to a specific cache instance in a distributed cache.
Published by: client applications
Subscribed to by: SolCache
#P2P/routerName/clientUsernameHash/#client/>
#P2P/routerName/clientUsernameHash/#client/CACHEMGR Used by SolCache instances to communicate with their Cache Manager.
Published by: SolCache
Subscribed to by: router (VMR Version 8.2.x or greater)
#P2P/routerName/#client/>
#P2P/routerName/#client/CACHEMGR Used by SolCache instances to communicate with their Cache Manager.
Published by: SolCache Instances
Subscribed to by: router (Solace VMRs prior to Version 8.2.x and on Solace appliances)
#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 router sets the prefix.
This topic is used by Solace VMRs Version 8.2.x or greater. 
Published by: client applications
Subscribed to by: client API
#P2P/v:routerName/clientName/> #P2P/v:routerName/clientName/... Used for Direct Messaging request/reply. The name space is controlled by the client API, but router sets the prefix.
This topic is used for Solace VMRs prior to Version 8.2.x and for Solace appliances. 
Published by: client applications
Subscribed to by: client API
#P2P/QUE/queueName #P2P/QUE/queueName 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 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 router 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. Name space is controlled by the client API, but router sets the prefix.
Published by: client applications
Subscribed to by: client applications
#P2P/v:routerName/> #P2P/v:routerName/... Subscription created when a virtual router is discovered, to attract #P2P traffic for the router.  This subscription is not visible in CLI.
Published by: client applications
Subscribed to by: router
#P2P/routerName/> #P2P/routerName/... Subscription always created when a physical router is discovered, to attract #P2P traffic  for the router. This subscription is not visible in CLI.
Published by: client applications
Subscribed to by: router
#SEMP/routerName/> #SEMP/routerName/SHOW
#SEMP/routerName//ADMIN/CLIENT
#SEMP/routerName/ADMIN/DISTRIBUTED-CACHE
Used to direct SEMP commands to a physical router name.
Published by: client applications
Subscribed to by: router
#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. Subscription is only present when a given router is active for the virtual router name.
Published by: client applications
Subscribed to by: router