| Author |
Message
|
| Svp |
 Posted: Thu Dec 02, 2010 9:48 am Post subject: Unable to get MQHRF2 properties in the message |
 |
|
Apprentice
Joined: 18 Feb 2010
Posts: 40
|
A MQTT client publishes a message with a topic which is subscribed by a queue(MQv7). The properties of the message says its a MQRFH2 format.
When my message flow(WMBv7) reads the message, the MQRFH2 is not set in the Message . The Properties,MQMD and BLOB are populated.
Could anyone suggest what would be the problem? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Dec 02, 2010 10:41 am Post subject: Re: Unable to get MQHRF2 properties in the message |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Svp wrote: |
| Could anyone suggest what would be the problem? |
I'm only guessing here, but could the contents of the RFH2 been turned into message properties by the v7 nature of the readign set up?
Aside from that, can the sending application prove that it's supplying an RFH2 (rather than just setting the format in the MQMD? Does your assertion that the message only contains Properties, MQMD & BLOB come from a user trace? What's the format shown in the MQMD?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Svp |
| Posted: Thu Dec 02, 2010 10:59 am Post subject: |
|
|
Apprentice
Joined: 18 Feb 2010
Posts: 40
|
When I checked the properites of the input message in MQ Explorer it has data in MQRFH2 Properties and Named Properties.
But the trace gives MQMD.Format is NULL. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 03, 2010 1:01 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Inspect the message before it hits the broker. Verify that the MQMD.Format field has the correct value for the RFH header.
Should the value still be null tell the sender to fix it. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Svp |
| Posted: Fri Dec 03, 2010 6:45 am Post subject: |
|
|
Apprentice
Joined: 18 Feb 2010
Posts: 40
|
When a MQTT Client publishes a topic based message, the Telemetry service running in WMQv7.0.1.3 generates MQRH2 Format when it receives. MQRFH2 format is not dependent on the Sender.
As I said earlier when I check the properties of the message in the MQ Explorer the MQRFH2 format is available with mqtt.clientId,mqtt.msgId & mqtt.qos .
I used RFHUTIL to check the same message in which RFH tab is empty and
UsrProp tab has
mqtt.clientId=client1
mqtt.qos=2
mqtt.msgid=1
MQTopicString=testTopic. |
|
| Back to top |
|
|
| JonLevell |
| Posted: Fri Dec 10, 2010 4:44 am Post subject: Properties can be RFH2 or not |
|
|
Newbie
Joined: 10 Dec 2010
Posts: 1
|
Properties can be including as part of the message (as an RFH2 header) or separately in a message handle so that the MQ APIs for parsing message properties can be used. By default applications which understand message properties (i.e. they supply a message handle) are given them in that format and other (e.g. older) applications are given the message with an RFH2 header
It sounds like some apps are getting the message with the properties and other are seeing an RFH2 header.
If you want to force an application to receive an RFH2 header - you can set the PROPCTL attribute (short for "Property Control") on the queue to be "FORCE" - which means force properties to be an RFH2.
Hope this helps...
Jon Levell
IBM Hursley |
|
| Back to top |
|
|
|
|
