Discover what is going wrong when an MQTT client is unexpectedly
disconnected from a telemetry channel.
Procedure
If your MQTT client connects successfully and later disconnects
with no apparent reason, consider the following reasons to diagnose
the problem:
- The queue manager, MQXR service, or telemetry channel is
not running.
Start the queue manager, MQXR service,
or telemetry channel. Try reconnecting the MQTT client, and check
that this solution rectifies the problem.
- Another client is started and connects with the same client
ID.
In this case, IBM® MQ accepts the connection from the
second MQTT client and forcefully disconnects the first MQTT client.
- The MQTT client accesses a topic that it is not authorized
to, either for publishing or subscribing.
IBM MQ disconnects the MQTT client.
- The TCP/IP connection is no longer active.
Diagnose
and fix the problem with your TCP/IP connection, and try reconnecting
the MQTT client.