MQ Telemetry troubleshooting

MQ Telemetry troubleshooting

Look for a troubleshooting task to help you solve a problem with running MQ Telemetry applications.

Location of telemetry logs, error logs, and configuration files
Find the logs, error logs, and configuration files used by MQ Telemetry.
Tracing the telemetry (MQXR) service
Follow these instructions to start a trace of the telemetry service, set the parameters that control the trace, and find the trace output.
System requirements for using SHA-2 cipher suites with MQTT channels
If we use a version of Java that supports SHA-2 cipher suites, we can use these suites to secure your MQTT (telemetry) channels and client apps.
Resolving problem: MQTT client does not connect
Resolve the problem of an MQTT client program failing to connect to the telemetry (MQXR) service.
Resolving problem: MQTT client connection dropped
Find out what is causing a client to throw unexpected ConnectionLost exceptions after successfully connecting and running for either a short or long while.
Resolving problem: Lost messages in an MQTT application
Resolve the problem of losing a message. Is the message non-persistent, sent to the wrong place, or never sent? A wrongly coded client program might lose messages.
Resolving problem: Telemetry (MQXR) service does not start
Resolve the problem of the telemetry (MQXR) service failing to start. Check the MQ Telemetry installation and no files are missing, moved, or have the wrong permissions. Check the paths that are used by the telemetry (MQXR) service locate the telemetry (MQXR) service programs.
Resolving problem: JAAS login module not called by the telemetry service
Find out if your JAAS login module is not being called by the telemetry (MQXR) service, and configure JAAS to correct the problem.
Parent topic: IBM MQ Troubleshooting and support

Related information

MQ Telemetry