| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Topic and MQTT Topic |
« View previous topic :: View next topic » |
| Author |
Message
|
| Prithviraj |
 Posted: Wed Feb 11, 2015 8:36 pm Post subject: MQ Topic and MQTT Topic |
 |
|
Apprentice
Joined: 29 May 2014
Posts: 30
|
Hi all,
In Websphere MQ Explorer, under any windows queue manager, we have a folder to create topics.
Is this topic in MQ is same as MQTT topic ?
When I am publishing, in a particular MQTT topic, from Arduino I am able to receive those messages from same MQ topics in Explorer. But if I am opening a MQTT client utility and subscribing the same MQTT topic in which Arduino is publishing, , the client gets disconnected when Arduino starts publishing. Why is it like this ? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Feb 18, 2015 6:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Ok.
MQTT is an entirely separate protocol from MQ.
The MQTT daemon that ships with MQ acts as a bridge between MQ and MQTT. So when you publish or subscribe to messages on MQ topics, those can be bridged to the same topic in MQTT - that is, to the same topic string not the same topic object. So you can publish or subscribe on topics in MQTT and they will get bridged to MQ.
So, MQ <-- bridge --> MQTT.
On the MQTT side, the bridge is just an MQTT broker. You can use it just to connect MQTT applications to other MQTT applications, without bridging to MQ at all. There are many better options for doing this, however - IBM Message Sight, for example (which also bridges to MQ).
I can't think of a particular reason why your client utility gets disconnected when your arduino starts publishing. I suspect it's an issue with the client utility. Have you tried the sample utility that comes with the MQTT bridge? |
|
| Back to top |
|
|
| sharathsis123 |
| Posted: Tue Mar 17, 2015 9:49 pm Post subject: |
|
|
Newbie
Joined: 17 Mar 2015
Posts: 2
|
Hi ,
Have configured the mqtt channel ? check whether the mqtt service is running ? check the status of system.mqtt.transmit.queue. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Mar 23, 2015 5:20 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Also, you should make sure that the arduino and the client are using different client ids when connecting to MQTT.
If they are the same, that will explain the problem. Each client must use a unique client ID or they will steal connections from each other. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
