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 » Debug Neon Message Parsing

Post new topic  Reply to topic
 Debug Neon Message Parsing « View previous topic :: View next topic » 
Author Message
mkhadse
PostPosted: Mon Jan 13, 2003 10:36 am    Post subject: Debug Neon Message Parsing Reply with quote

Acolyte

Joined: 31 Dec 1969
Posts: 73
When I run a trace on MQSI, I see that the flow is stuck in compute node on a specific statement. This statement assigns data to an output XML element from an Neon Message. How can I find out hat is wrong with the input message?

I also tried the Neon utility - apitest with the same input message and it core dumps.

I am using MQSI 2.0.2 on AIX.

Thanks
Back to top
View user's profile Send private message
mkhadse
PostPosted: Tue Jan 14, 2003 8:22 am    Post subject: Reply with quote

Acolyte

Joined: 31 Dec 1969
Posts: 73
I see that all of the elements are optional and each such elements are mandatory elements inside it.

Is this the reason why neon might be hung-up processing?
Back to top
View user's profile Send private message
Paul D
PostPosted: Tue Jan 21, 2003 6:58 am    Post subject: Reply with quote

Master

Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
Do a trace node before the compute node and run a user trace and see what the message tree looks like (Set to ${Root}). The MQInput node does the NNSY input format parse. If you are past that, then you made it past the input format. NNSY does the hand off to MQSI coming out of that on the out terminal. I'm assuming that you are just using the MQInput Nodes and not any of the NNSY nodes (NEON*).
Back to top
View user's profile Send private message Visit poster's website
yaakovd
PostPosted: Tue Jan 21, 2003 11:15 am    Post subject: Reply with quote

Partisan

Joined: 20 Jan 2003
Posts: 319
Location: Israel
Hi Milind

In this case you must at least one mandatory element after "bad data".
Otherwise NEON has to match possible options and it lost its mind

Set last segment in message format to mandatory and you will get correct error message.
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Debug Neon Message Parsing
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.