| Author |
Message
|
| amit_talpade_star |
 Posted: Thu Dec 16, 2004 10:55 am Post subject: message modelling errors |
 |
|
Apprentice
Joined: 14 Dec 2004
Posts: 39
|
I am working on WBI MB 5 FP4
Trying to build my own message definition. Using the EDIFACT to XML sample as a reference
The following EDIFACT conversion is my "hello world" attempt at the EDIFACT to XML transformation.
MUNB+IATA:1+0AMUA+NHMUA+150805:1707+123456789ABCDE'
I am getting errors after defining a message set and setting
...SET OutputRoot.Properties.MessageFormat = 'XML';... in the message flow for the transformation
The errors are
No Message Id received in TDS Parser Initialization
The TDS worker is not receiving a proper Message Id parameter during initialization.
Ensure that the message identifier used in your message matches the message as defined in the Message Brokers Toolkit.
Message Translation Interface Parsing Errors have occurred:
Message Set Name : 'TestEDIFACT'
Message Set Level : '1'
Message Format : 'EDIFACT'
Message Type Path : 'EDIFACTMSG/EDIFACTMESSAGE'
Review further error messages for an indication to the cause of the errors.
An error occurred in parser 'Root' whilst parsing the field named 'MRM' on behalf of node 'EDIFACT2XML.MQInput'. The data being parsed was '4d442020020000000000000008000000ffffffff0000000022020000b50100004d515354522020200000000000000000414d51205742495f515f4d20202020203d5cb94120003436000000000000000000000000000000000000000000000000000000002020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020205742495f515f4d202020202020202020202020202020202020202020202020202020202020202020202020202020202077626975736572202020202016010515000000f094c85ff239b634828ba628f203000000000000000000000b20202020202020202020202020202020202020202020202020202020202020200b000000433a5c57494e444f57535c73797374656d33325c6d6d632e657865203230303431323136313833393534333820202020000000000000000000000000000000000000000000000000010000000000000000000000ffffffff554e422b494154413a312b30414d55412b4e484d55412b3135303830353a313730372b313233343536373839414243444527'.
This message gives the name of the field in the parser that was being parsed at the time the error occurred.
You should check for other messages issued with this one for the full context of the error.
Exception condition detected on input node: 'EDIFACT2XML.MQInput'.
Node 'EDIFACT2XML.MQInput' has received a message, but an exception was generated whilst initializing it's internal representation. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node.
If 'complete' or 'immediate' MRM message body validation is being applied to messages received by this node, it's possible the format of the body of the received message is invalid. Examine further messages for confirmation of this or to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.
Any help would be most appreciated |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Dec 16, 2004 10:59 am Post subject: Re: message modelling errors |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| amit_talpade_star wrote: |
| Review further error messages for an indication to the cause of the errors. |
| amit_talpade_star wrote: |
| This message gives the name of the field in the parser that was being parsed at the time the error occurred. |
| amit_talpade_star wrote: |
| Message Type Path : 'EDIFACTMSG/EDIFACTMESSAGE' |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| amit_talpade_star |
| Posted: Thu Dec 16, 2004 11:35 am Post subject: |
|
|
Apprentice
Joined: 14 Dec 2004
Posts: 39
|
I had already set the message type in the mqinput node as you have suggested
I wanted to know ...what the following entails....
"No Message Id received in TDS Parser Initialization
The TDS worker is not receiving a proper Message Id parameter during initialization.
Ensure that the message identifier used in your message matches the message as defined in the Message Brokers Toolkit."
Also The EDIFACT Sample which I have deployed works...In the code for that I do not see any message ID being set.
Any pointers please ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 16, 2004 11:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes.
Review the logs.
You did not post the error message that included the actual error information.
The parser had some difficulty parsing either the field EDIFACTMESSAGE or the next defined field.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| amit_talpade_star |
| Posted: Thu Dec 16, 2004 11:49 am Post subject: |
|
|
Apprentice
Joined: 14 Dec 2004
Posts: 39
|
I cleaned the event viewer app logs
submitted an edifact message on input queue and got an error. message got deposited to backout queue
then i checked my event viewer and this is what i have
( WBRK_BROKER.wbiuser ) No Message Id received in TDS Parser Initialization
The TDS worker is not receiving a proper Message Id parameter during initialization.
Ensure that the message identifier used in your message matches the message as defined in the Message Brokers Toolkit.
( WBRK_BROKER.wbiuser ) Message Translation Interface Parsing Errors have occurred:
Message Set Name : 'TestEDIFACT'
Message Set Level : '1'
Message Format : 'EDIFACT'
Message Type Path : 'EDIFACTMSG/EDIFACTMESSAGE'
Review further error messages for an indication to the cause of the errors.
( WBRK_BROKER.wbiuser ) An error occurred in parser 'Root' whilst parsing the field named 'MRM' on behalf of node 'EDIFACT2XML.MQInput'. The data being parsed was '4d442020020000000000000008000000ffffffff0000000022020000b50100004d515354522020200000000000000000414d51205742495f515f4d20202020203d5cb94120003471000000000000000000000000000000000000000000000000000000002020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020205742495f515f4d202020202020202020202020202020202020202020202020202020202020202020202020202020202077626975736572202020202016010515000000f094c85ff239b634828ba628f203000000000000000000000b20202020202020202020202020202020202020202020202020202020202020200b000000433a5c57494e444f57535c73797374656d33325c6d6d632e657865203230303431323136313934363034383520202020000000000000000000000000000000000000000000000000010000000000000000000000ffffffff554e422b494154413a312b30414d55412b4e484d55412b3135303830353a313730372b313233343536373839414243444527'.
This message gives the name of the field in the parser that was being parsed at the time the error occurred.
You should check for other messages issued with this one for the full context of the error.
( WBRK_BROKER.wbiuser ) Exception condition detected on input node: 'EDIFACT2XML.MQInput'.
Node 'EDIFACT2XML.MQInput' has received a message, but an exception was generated whilst initializing it's internal representation. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node.
If 'complete' or 'immediate' MRM message body validation is being applied to messages received by this node, it's possible the format of the body of the received message is invalid. Examine further messages for confirmation of this or to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.
Is there some other place to check for logs ?
Please advise |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Dec 16, 2004 11:32 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Please verify following properties for your message set,
1. Message Set (DXXXX)
2. Message Type
3. Message Format (XML, TDS, etc)
Make sure you are entering correct values in your MQInput node.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
