Application debugging
- Last UpdatedApr 24, 2025
- 1 minute read
The following topics can be published to, to provide additional application-specific information or detailed logs of the local PubSub Engine. When publishing to messages, the value published can be any string. In most cases, the details are sent to the PSengine.log file.
|
Topic |
Description |
|---|---|
|
pubsub.debug.apptrace.<processId> |
Start tracing a given application. All messages sent, received, or blocked due to security will be logged. Note: This topic can be very noisy. To turn it off, send the same message with a Process ID of 0. |
|
pubsub.debug.appdump.<processId> |
Log information about the application, including the cache of allowed security groups, all outstanding subscriptions, and all outstanding publications. |
|
pubsub.debug.publishsecurity |
Dump out a list of all secured topics and the group to which they are secured. |
|
pubsub.debug.apprefreshsecurity.<pid> |
Request the applications transmit thread to refresh its security cache. The refresh will not occur until the application receives a message to wake up the transmit thread. Note: Proceed with caution when using this topic. It should be a last resort. |
|
<system>.realtime.cmxpersistencestore.dumptree |
If you publish on this topic, the CMX Persistence Store process will dump all the current RealTime subscriptions to the cmxpersistencestore.log file. Note: This can take a lot of time on large systems and slow down the PubSub Engine. Caution should be taken when publishing to this topic. |