| Author |
Message
|
| wessam_sosa |
 Posted: Wed Nov 01, 2006 6:24 am Post subject: EDIFACT error in debuging |
 |
|
Apprentice
Joined: 01 Nov 2006
Posts: 32
|
| Quote: |
i`m using WBIMB v.6,i created a message set and message flow that converts from EDIFACT to XML,i successed to deploy it in broker,but when i debug this exception appears:
ParserException
File = F:\\build\\S000_P\\src\\cpi\\pwf\\nxd\\nxdparser.cpp
Line = 155
Function = NXDParser::initializeParse
Type =
Name =
Label =
Catalog = BIPv600
Severity = 3
Number = 5424
Text = No Message Id Received
what can i do? |
[/quote] |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Nov 01, 2006 1:36 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
|
Set Properties.MessageType to the name of your message definition. You can do this on the Default page of the input node properties, or using an RFH2 header. |
|
| Back to top |
|
|
| wessam_sosa |
| Posted: Thu Nov 02, 2006 1:22 am Post subject: another exception |
|
|
Apprentice
Joined: 01 Nov 2006
Posts: 32
|
Thanks alot,when i did that another exception appears:
ParserException
File = F:\\build\\S000_P\\src\\MTI\\MTIforBroker\\MtiImbParser2\\MtiImbFIHandler.cpp
Line = 998
Function = MtiImbFIHandler::endMessageContent
Type =
Name =
Label =
Catalog = BIPv600
Severity = 3
Number = 5288
Text = MTI. Not all the buffer was used when reading message
I hope you reply |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Nov 02, 2006 2:32 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
That's a completely different error. At least you have sorted out the first one.
To debug BIP5288, you need to gradually shorten the message until it parses successfully. The message tree will be incorrect, but at least you will be able to see what the parser has done wrong. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 02, 2006 2:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
A trace node usually shows the last field that the parser successfully processed.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 02, 2006 3:37 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And the problem may be as simple as converting correctly the CRLF when using FTP to send the message to the broker....
We had the problem where a number of things were loaded into a DB from a file. The end of record was a CRLF. The file was ftp'd from wintel to Unix to be loaded into the DB. That part worked fine but the broker had the exact complaint you have. It means that the stream has more information than what the message definition says (especially on a CWF format).
They had to ftp the file again in text mode (ascii) to have the correct CRLF for Unix, reload it to the DB and then the text was in the right length for the broker to parse. Difference in length of the field in the DB was 1 char.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wessam_sosa |
| Posted: Sun Nov 05, 2006 2:22 am Post subject: i did what u said |
|
|
Apprentice
Joined: 01 Nov 2006
Posts: 32
|
| i shorted the message alot and the same exception appeared,i put the trace node it gave me unresolved choice,sorry for disturbing you,please give me a help,thanks alot |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Nov 05, 2006 6:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Unresolved choice is a different exception.
Check out your message model. Somewhere in the definition you have a choice for the way the tree should look. Check your message against it.
Choice means you have one of the options, not none (unless having nothing underneath is one of the options), and not more than one...
Fix your message or your message model.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Nov 07, 2006 2:36 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| i shorted the message alot and the same exception appeared,i put the trace node it gave me unresolved choice,sorry for disturbing you,please give me a help,thanks alot |
Keep going. Shorten it some more. Keep shortening it until you get a successful parse ( you will, eventually ).
(This exception is caused by an error in your TDS message definition. The parser reaches the end of the model before it has consumed all of the bitstream. So you will need to change your model - but first, you need to find out what the problem is.) |
|
| Back to top |
|
|
|
|
