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 » Putting Message fails After parsing Failure (AIX)

Post new topic  Reply to topic
 Putting Message fails After parsing Failure (AIX) « View previous topic :: View next topic » 
Author Message
vikashsharma85
PostPosted: Wed Jun 23, 2010 3:25 am    Post subject: Putting Message fails After parsing Failure (AIX) Reply with quote

Novice

Joined: 19 Mar 2010
Posts: 15

We need to store the failed message in another Queue for Further investigation.
This Scenario is working fine in Windows Broker and issue is only being faced in AIX.

We have disable the validate property of OutputQueue.

We are unable to put the failed message as, while putting the message it tries to re parse the message.
We had tried with following options:
1) Removing the properties from MCD folder in a compute node, before putting the message, we were successful in removing message set,type and format. But depending on the payload copied, compute node was automatically updating domain property in MCD.
2) we tried to convert the MRM domain Message in to BLOB, using ASBITSTREAM function,In the compute mode prior to putting the message in the Output Queue. I have used following code in the compute node:

Code:
   SET OutputRoot.BLOB.UnknownParserName = '';
   SET OutputRoot.BLOB.BLOB = ASBITSTREAM(InputBody);


But this approach gave this exception,
Code:

Severity:INTEGER:3
Number:INTEGER:5136
Text:CHARACTER:Invalid Wire format retrieved.


Please provide some solution to handle this scenario.
Back to top
View user's profile Send private message
kimbert
PostPosted: Wed Jun 23, 2010 5:47 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

That is not the error message - it is just the summary line from the system log. Look up BIP5136 ( Google should be able to help you ) or take a user trace to see the full text of the error message.

I suggest that you read the infocenter topic on ASBITSTREAM, or perhaps use the search button on this form. There are dozens of examples that show how to use ASBITSTREAM correctly.
Back to top
View user's profile Send private message
vikashsharma85
PostPosted: Thu Jun 24, 2010 8:14 pm    Post subject: Reply with quote

Novice

Joined: 19 Mar 2010
Posts: 15

Hi,

Thanks for the response.

I would like to be more specific about the issue we are facing.

We have a requirement to store the failure messages in a Queue for further investigation.

Broker Behavior for Parsing:
Input Node: It converts inputbitStream in to Logical Tree based on the Parser and Message set Specified.

Output Node: It Converts logical tree in to Bit stream using the Parser and Message set in the message.


Now, The issue we are facing is while putting the parsing failed message on the Output Queue as it is unable to convert it in to bitstream as the message is invalid.

This Issue, is only visible on AIX broker, and it works fine on windows broker. Can you provide some work around for AIX or we should open A PMR for this issue.

Thanks....
Back to top
View user's profile Send private message
smdavies99
PostPosted: Thu Jun 24, 2010 9:34 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

If you want to store the input message on a Queue in the event of a failure in an 'As arrived' form then you need to change your flow.

InputNode (Parse as BLOB)->Comput Node (Saves InputRoot to somewhere in the Environment tree)-> RCD node to parse using the Message set etc that you currently have in the InputNode.

Then when you get a failure, all you need to do is restore the saved inputRoot tree to the output root in a compute node and pass it to a MQOutputNode.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
kimbert
PostPosted: Thu Jun 24, 2010 11:20 pm    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

smdavies99 said:
Quote:
If you want to store the input message on a Queue in the event of a failure in an 'As arrived' form then you need to change your flow.
I agree - his suggested approach is a standard pattern in message flows.
Back to top
View user's profile Send private message
vikashsharma85
PostPosted: Sat Jun 26, 2010 9:17 am    Post subject: Reply with quote

Novice

Joined: 19 Mar 2010
Posts: 15

Hi Thx All,

It Worked...
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 » Putting Message fails After parsing Failure (AIX)
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.