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 » No parsing on the input node?

Post new topic  Reply to topic
 No parsing on the input node? « View previous topic :: View next topic » 
Author Message
Boolean
PostPosted: Mon Nov 10, 2003 3:24 am    Post subject: No parsing on the input node? Reply with quote

Acolyte

Joined: 05 Jun 2003
Posts: 56
Location: Sweden

Using WBI MB 5.0 I have one input node, one compute node (copy entire message) and one output node.
The input node uses a message set (MRM-TDS).

A test file is written on the input queue and the message arrives at the output queue ok.

But! When a trace node is inserted after the input node, the message goes DLQ and parsing error appears.

I thought that parsing was done on the input node. Why does the syntax checking occur first when there is a trace node present?????

/ Boolean (Anders)
Back to top
View user's profile Send private message
vmcgloin
PostPosted: Mon Nov 10, 2003 4:51 am    Post subject: Reply with quote

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

Parsing is only done on the input node if you have validation turned on - see the properties of the input node. Also, the message is not parsed in the compute node you describe since it just performs a straight copy.
So the trace node is the first time the message is parsed.

Cheers,
Vicky
Back to top
View user's profile Send private message
kimbert
PostPosted: Mon Nov 10, 2003 4:53 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

WMQI utilises a partial parsing technique. No parsing is done until a field in the message is accessed. Parsing then proceeds as far as is necessary to satisfy the field access. Most of the time this behaviour is completely invisible, but occasionally (like in your scenario) its worth knowing about. In your message flow, you simply copied the entire message from input to output, so WMQI simply copied the bitstream without doing any parsing. Adding a trace node forced the entire message to be parsed, and you then saw the parsing exception.

In future, if you want to check whether your message model is correct using a trivial Input-Compute-Output flow, go to the MQInput node properties, and on the Validation tab, set validation to 'Complete'. This will trigger a full parse.
Or use the debugger, which is even easier...
Back to top
View user's profile Send private message
Boolean
PostPosted: Mon Nov 10, 2003 5:14 am    Post subject: Reply with quote

Acolyte

Joined: 05 Jun 2003
Posts: 56
Location: Sweden

Of course!
Validate was set to "none" on the input node.
Thank's for enlighting me!

/Anders (Boolean)
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 » No parsing on the input node?
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.