| Author |
Message
|
| wessam_sosa |
 Posted: Thu Nov 09, 2006 3:54 am Post subject: parsing exception |
 |
|
Apprentice
Joined: 01 Nov 2006
Posts: 32
|
i`m converting from EDIFACT to XML,i made the parsing time of the MQInput node is immediate, and this exception appears when debuging in the MRM:
ImbRecoverableException caught from worker->initializeParse/setFIHandler.
and with this exception there is the exception in the exception list:
MTI. Not all the buffer was used when reading message
what can i do? plz HELP |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Nov 09, 2006 4:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Search this site. I already answered the exact same question from somebody else. Check your data length. Make sure if the record terminator is EOL that you do not have a cross platform problem (like when doing a file FTP in binary instead of ASCII).
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Nov 09, 2006 4:51 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
|
| Back to top |
|
|
| wessam_sosa |
| Posted: Thu Nov 09, 2006 5:47 am Post subject: i did !! |
|
|
Apprentice
Joined: 01 Nov 2006
Posts: 32
|
i did what u said,and th exception disappeared then there is another exception appeared in the MRM which is :
ImbRecoverableException caught from worker->parseNext.
then i made in the MQInput node the parsing time Immediate, so the exception i sent before appeared again,i had shorten the message alot that i can`t short it more,i disabled all the unbounded elements in the XML schema. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 09, 2006 5:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You need to keep troubleshooting each problem.
You need to get training on this product.
You need to go back and read the sections in the Information Center on Developing Message Models again.
You need ot keep looking up the BIP numbers in the Diagnostic Messages tool in the Info Center, and thinking about what it says and thinking about what you're trying to do and thinking about what it probably means.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Nov 09, 2006 6:40 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| i did what u said,and th exception disappeared |
Yes - you probably shortened the message too much, and received an error saying that the bitstream is too short. So lengthen the bitstream until you get a successful parse. This is really not all that difficult - please start thinking about the problem yourself.
When you get the length adjusted so that no more exceptions are thrown, you will get a message tree. it will be incorrect, because your model is incorrect. But at least you will be able to look at the message tree and see where the parsing is going wrong. |
|
| Back to top |
|
|
| wessam_sosa |
| Posted: Sun Nov 12, 2006 2:36 am Post subject: new exception |
|
|
Apprentice
Joined: 01 Nov 2006
Posts: 32
|
when i made in the MQInput node the parsing time "complete" and the validation " content and value" this exception appears:
An unresolved entity has been encountered in the bitstream, with validateTiming set to complete
what does it mean? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Nov 12, 2006 4:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What is the BIP number for that error?
What does the documentation for that error say?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wessam_sosa |
| Posted: Sun Nov 12, 2006 4:43 am Post subject: BIP |
|
|
Apprentice
Joined: 01 Nov 2006
Posts: 32
|
|
| Back to top |
|
|
| wessam_sosa |
| Posted: Sun Nov 12, 2006 7:18 am Post subject: |
|
|
Apprentice
Joined: 01 Nov 2006
Posts: 32
|
I configured the physical properties of the elements of the definition file ( i typed the tags), it parses the first part of the message and it appears in the exception list the following exception (BIP5505):
CPI Converter Input Data Invalid
how does the data pattern typed? |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Nov 13, 2006 4:31 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
hi wessam_sosa,
You need to provide a lot more information about what you are doing. Your last post was talking about BIP5376. Now you are talking about BIP5505. I do not understand why you are asking about BIP5505. I do not know whether BIP5376 has stopped happening.
If you still need help, take a user trace while parsing a message. Post the full text of the parsing exceptions here (not the entire user trace!) . You will get much better error messages that way, and we will be able to help. |
|
| Back to top |
|
|
| wessam_sosa |
| Posted: Mon Nov 13, 2006 6:52 am Post subject: |
|
|
Apprentice
Joined: 01 Nov 2006
Posts: 32
|
hi,
the BIP5376 has been resolved,now the BIP5505 is stopped with me,there a part of the message is parsed in a wrong way,and there is a convertion exception,that is:
Message
Properties
MQMD
MRM
UNB
S001
UNB_0001 = UNB+UNOA
LocalEnvironment
Environment
ExceptionList
ParserException
File = F:\\build\\S000_P\\src\\DataFlowEngine\\ImbRootParser.cpp
Line = 551
Function = ImbRootParser::parseNextItem
Type = ComIbmMQInputNode
Name = bappflow#FCMComposite_1_1
Label = bappflow.MQInput
Catalog = BIPv600
Severity = 2
Number = 5902
Text = Exception whilst parsing
Insert
Insert
Insert
ParserException
File = F:\\build\\S000_P\\src\\MTI\\MTIforBroker\\MtiImbParser2\\MtiImbParser.cpp
Line = 445
Function = MtiImbParser::parseFirstChild
Type = ComIbmMQInputNode
Name = bappflow#FCMComposite_1_1
Label = bappflow.MQInput
Catalog = BIPv600
Severity = 3
Number = 5285
Text = ImbRecoverableException caught from worker->parseNext.
Insert
Insert
Insert
Insert
ParserException
File = F:\\build\\S000_P\\src\\cpi\\pwf\\nxd\\nxdworker.cpp
Line = 456
Function = NXDWorker::parseNext
Type =
Name =
Label =
Catalog = BIPv600
Severity = 3
Number = 5421
Text = TDS General Error
Insert
Insert
Insert
ConversionException
File = F:\\build\\S000_P\\src\\cpi\\bsutils\\datacnv.cpp
Line = 599
Function = DataCnv::StrToInt64
Type =
Name =
Label =
Catalog = BIPv600
Severity = 3
Number = 5505
Text = CPI Converter Input Data Invalid
Insert
Insert
plz I need some information about configuring the physical properties to the EDIFACT,thanks alot |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 13, 2006 3:22 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
You will have to look at the inserts to find out which field this is happening on but the error seems quite clear:
| Quote: |
Conversion Exception
DataCnv::StrToInt64 |
Could it be that the string supplied for the field is not numeric or not an Integer ?
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wessam_sosa |
| Posted: Wed Nov 15, 2006 12:50 am Post subject: |
|
|
Apprentice
Joined: 01 Nov 2006
Posts: 32
|
Hi,
it is supposed that it is an integer no. but toke as a string so a big part of the message toke in the field while its length is only 1 |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Nov 15, 2006 4:22 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| plz I need some information about configuring the physical properties to the EDIFACT |
Have you looked at the EDIFACT sample? |
|
| Back to top |
|
|
|
|
