|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Broker 6 Pub/Sub issue |
« View previous topic :: View next topic » |
Author |
Message
|
hayderr |
Posted: Mon May 14, 2007 3:57 pm Post subject: Broker 6 Pub/Sub issue |
|
|
Novice
Joined: 14 May 2007 Posts: 22
|
Hi,
I am a new member on this forum, I have visited this forum everytime I face a problem with Message Broker, and I find a solution after brwosing it.
I am using Message Broker 6 to develop an application, and using a Pub/Sub approach. The protocol I am using is MQTT. The problem I am facing is, sometimes when I publish a message the client (MQTT client, C API) dosent receive the message. The client is saying I am listening to the network, however they are saying the Broker never pushed the message to the subscriber.
I have enabled a user trace on my Broker, and the message I get is below:
2007-05-10 14:20:13.760802 8096 UserTrace BIP7080I: Node 'MQTTSender.MQTTSender.SendToTanker.ComIbmPSService': The Publication Node with Subscription Point '''' has received a message of type 'Publish'.
The Publication Node with Subscription Point '''' has started processing a message.
No user action required.
2007-05-10 14:20:13.760802 8096 UserTrace BIP7082I: Node 'MQTTSender.MQTTSender.SendToTanker.ComIbmPSService': Publishing to destination '#MQe#SC#Scada:2,1883:033336370000000000000000000000000000000000000000' for user '367'.
A publication destination is being added to the list of destinations to '#MQe#SC#Scada:2,1883:033336370000000000000000000000000000000000000000' for user '367'.
No user action required.
2007-05-10 14:20:13.762802 8096 UserTrace BIP7085I: Node 'MQTTSender.MQTTSender.SendToTanker.ComIbmPSService': The Publication Node has propagated a message to its output terminal for subscription point ''''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
This was never received by the client. The client had the higher trace on, and is saying that nothing has been available to be delivered.
To cut short, my question is, I understand there is undercover communication between the Broker and the client (messages go forward and backward) PUBLISH, PUBREC, PUBREL, and PUBCOMP. wherre can I find these messages? Or how can I diagnose more about this issue?
I am using QoS 2.
Your help is much appreciated, Thank you |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon May 14, 2007 4:16 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I don't know a lot about MQTT... so this is just general purpose pub/sub advice...
The usual cause of a publication not being delivered is that there wasn't an active subscriber...
A good trick to help you see what's going on is to create a simple subscriber that will store messages in a database or etc, and subscribe it to every topic or every topic of interest. Then you'll be able to know if the publisher had an issue, or the subscriber had an issue.
You can also ask broker for report messages when you publish - it won't tell you if there were any subscribers, but it will tell you if broker had an error processing your publication. _________________ I am *not* the model of the modern major general. |
|
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
|
|
|
|