| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Parsing problem: v2.1, RFH2 related |
« View previous topic :: View next topic » |
| Author |
Message
|
| cadenza |
 Posted: Tue May 03, 2005 11:27 pm Post subject: Message Parsing problem: v2.1, RFH2 related |
 |
|
Apprentice
Joined: 01 Jun 2004
Posts: 48
|
Hi All,
I am using WMQI 2.1, CSD 07.
I am converting input XML files to '/' delimited message in the output. Recently we started recieving input messages containing RFH2 header data.
The problem identified from the trace file is that the parser is failing to navigate to the message body elements. The resultant output obtained is the header data along with a series of delimiters something like "RFH ... <psc> ... </psc>.. <mcd> ... </mcd> //////...."
I am unable to understand why it is happening this way. I have a gut feeling that since the header "looks" similiar to XML : <psc> ... </psc> etc. does it consider the header data to be the message body? If so then is there any way to help the parser know that it should expect an RFH2 header before the message body? Do you think that I need to strip the RFH2 header in the input and parse it and then re-attach it to the output message.
Awaiting for your kind suggestions.
Thanks. |
|
| Back to top |
|
 |
| EddieA |
| Posted: Wed May 04, 2005 12:03 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
It sounds like the Format fiels in the MQMD is not filled in correctly to identify that an RFH2 header is present. Otherwise, WMQI will parse out the RFH2 to a seperate tree structure.
What does a Trace of {Root} show for the MQMD Format field.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| cadenza |
| Posted: Wed May 04, 2005 12:59 am Post subject: |
|
|
Apprentice
Joined: 01 Jun 2004
Posts: 48
|
Hi Eddie,
I checked the trace node data before the compute as well as after the compute node. In both cases I found that the Format value of MQMD is set to 'MQHRF2 ' which indicates RFH2 header. |
|
| Back to top |
|
|
| cadenza |
| Posted: Wed May 04, 2005 1:23 am Post subject: |
|
|
Apprentice
Joined: 01 Jun 2004
Posts: 48
|
Hi All,
Just to update you of the status of the problem, I have tried the following:
1. Copied the message to my editor and sent the message through RFHUTIL along with the header data. (Currently the message is being put to the queue by another application).
Result: The messages landed up in failure queue. The error reported was that the parser was expecting the root element to be <xyz> but found <psc> instead.
2. Deleted the header part and sent it through RFHUTIL.
Result: Received the proper and desirable output.
However I am clueless as to how to solve the problem, because the messages are actually going to be sent by the application directly along with the header and not through RFHUtil  |
|
| Back to top |
|
|
| cadenza |
| Posted: Wed May 04, 2005 3:31 am Post subject: |
|
|
Apprentice
Joined: 01 Jun 2004
Posts: 48
|
Hi All,
Solved the problem!!!!! 
The problem was traced to the RFH2 header itself. The mcd folder value in the header was set to "none". This caused the parser to treat the message as a BLOB instead of MRM.
So, it could not navigate through the message tree. On changing the mcd folder values like setting the message domain to MRM format to XMl etc it worked.
Thanks to all for your support. |
|
| 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
|
|
|
|
