| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| RFH2 and missing body |
« View previous topic :: View next topic » |
| Author |
Message
|
| RogerLacroix |
 Posted: Tue May 15, 2007 9:28 am Post subject: RFH2 and missing body |
 |
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
I'm trying to help someone out.
Is a RFH2 message with a complete RFH2 header, mcd folder and jms folder but does not have a message body (payload) a valid RFH2 message?
If a RFH2 message has an empty message body, does it include the length field of the message body (i.e. set to zero)? Or is the length field omitted because there is no message body?
They are trying to determine which of these messages are invalid.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue May 15, 2007 9:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I don't think the RFH2 header specifies what makes a message "valid" or not...
And MQ doesn't care if the message body is empty or not.
As to what the length field will be set to, that depends on the application that created the MQRFH2.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue May 15, 2007 9:46 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
Its between the MQ broker and a JMS application. They are creating nodes (development work) in the broker and some of the messages are showing up in a strange format.
So they are trying to figure out if the developer has made a mistake or it is something else.
Also, should a JMS application be able to consume these types of messages or should they go to a 'bad message queue'.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue May 15, 2007 7:04 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| RogerLacroix wrote: |
Hi,
Its between the MQ broker and a JMS application. They are creating nodes (development work) in the broker and some of the messages are showing up in a strange format.
So they are trying to figure out if the developer has made a mistake or it is something else.
Also, should a JMS application be able to consume these types of messages or should they go to a 'bad message queue'.
Regards,
Roger Lacroix |
Roger,
having had a little bit of experience in this field, here is what we did:
To determine what a correct message (from the broker) should look like:
- You need somebody on the team who understands how MQ handles the headers and chains them...
- Have a regular JMS application create the input message to the flow....
- Examine the message and the headers in the flow.(trace / debug)
- Have a regular JMS application (proof of concept) create the output message of the flow
- Send that output message through a dummy flow to inspect the RFH2 as the broker shows it...
- Have the flow simulate that type of RFH2 for the content...
- Finally if the content of the RFH2 is not relevant to the consumer JMS application you can omit it entirely as JMS will just as well consume a message without JMS header as with JMS header....
- When suppressing an RFH2 header make sure you keep the CCSID, encoding and format to backfill on the preceding header you are keeping.
In our case we will have to alter a little bit the RFH being put on the publish by the broker so that the JMS topic does not appear as null....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed May 16, 2007 9:22 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Roger, What length are you referring to. There's no field that includes the payload, only the length of the RFH2 itself.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| 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
|
|
|
|
