Troubleshoot a PubSub application

Application-specific information can be logged on demand for a particular application, by publishing to a special topic. This topic includes the application’s process identifier (represented as <PID>) in the name:

1. To log the application’s current security groups, subscriptions, and publications, publish any data (it does not matter what) to the pubsub.debug.appdump.<PID> topic.

2. To continuously log the messages sent, received, or blocked due to security, publish any data to the pubsub.debug.apptrace.<PID> topic. Only one application can be traced at a time, and the output can be verbose, so it should not be left turned on for too long.

   To stop logging messages, replace the <PID> in the topic with the number 0, and then republish the data.

For more information, refer to PubSub debugging.