ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » ParserException: Innvalid MQRFH2

Post new topic  Reply to topic
 ParserException: Innvalid MQRFH2 « View previous topic :: View next topic » 
Author Message
SKK
PostPosted: Tue Sep 06, 2005 11:56 am    Post subject: ParserException: Innvalid MQRFH2 Reply with quote

Acolyte

Joined: 09 May 2005
Posts: 67

Hi,

our Application puts an invalid MQRFH2 in message. Because of this, MQSI 2.1 is unable to parse the message and the message goes to failure node.

Below is the error from trace log.
-------------------------------------

ParserException BIP6043E: Invalid folder size of '59' detected within an MQSeries RFH2 header.
MQSeries RFH2 headers require that the folder size must be a multiple of four bytes and must not be negative. The message being processed did not conform to this rule.
Correct the application (or compute expression) that generated the message.


Now, since we cannot make any changes to Application (third party software). Can anyway in MQSI, i can ignore/avoid the RFH2 Header and work with body of message.


Regards
Suresh.
Back to top
View user's profile Send private message
EddieA
PostPosted: Tue Sep 06, 2005 10:18 pm    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

Quote:
Can anyway in MQSI, i can ignore/avoid the RFH2 Header and work with body of message

Declare the mesage as a BLOB, remove the "offending" RFH2, and then parse the data. But, that assumes you know how long the RFH2 is in all cases. Unless you want to extract the length from within the BLOB and use that.

Failing that, go back to whoever is producing the message and tell them that it is an invalid message.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
SKK
PostPosted: Wed Sep 07, 2005 6:55 am    Post subject: Reply with quote

Acolyte

Joined: 09 May 2005
Posts: 67

Eddie,

I had tried that. It didn't work either. On the compute node for parsing the BLOB message, it encounters parser exception and says invalid RFH2 header and the message goes to failure node.


Regards
KK
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Sep 07, 2005 7:03 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Are you able to, as a test, use something like amqsget or amqsbcg to retrieve these messages?

If this is a COTS application producing the bad header, then you should file a bug with the vendor. If this is an inhouse application, then you should file a bug with them and refuse to process their data until they fix it.

You may need to put together a filter process - outside of broker - to fix this. I do not know of a way, myself, to instruct broker to IGNORE the RFH2 if it's there.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
EddieA
PostPosted: Wed Sep 07, 2005 12:17 pm    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

If it doesn't fail until you try and parse the message, start with a Compute that zaps the MQMD Format.

But as has been pointed out, the real solution is to get the message fixed.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
SKK
PostPosted: Wed Sep 07, 2005 1:25 pm    Post subject: Reply with quote

Acolyte

Joined: 09 May 2005
Posts: 67

Hi,

Its not an inhouse application. so nothing cannot be done on application side. I had even tried to ZAP the MQMD format in a compute node before actual parsing of message. But, again no luck, i get Parser exception.

As of now as temporary solution, i have written script which removes the invalid RFH2 header and places the message on Queue. But this cannot be implemeted in production.

Regards
KK
Back to top
View user's profile Send private message
EddieA
PostPosted: Wed Sep 07, 2005 4:51 pm    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

Quote:
But this cannot be implemeted in production

But you are quite happy to use a third party product that sends you invalid data that they will not fix.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » ParserException: Innvalid MQRFH2
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.