| Author |
Message
|
| francoisvdm |
 Posted: Wed Jul 05, 2006 6:17 am Post subject: |
 |
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
Thanks, learning something new everyday! 
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jul 05, 2006 4:56 pm Post subject: Re: MRM XML Validation Error Using Validate Node in WMB 6.0 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| jboller001 wrote: |
This results in the following excepiton details:
(0x01000000):ParserException = (
(0x03000000):File = 'F:\build\S600_P\src\MTI\MTIforBroker\MtiImbParser2\MtiImbTreeIterator.cpp'
(0x03000000):Line = 1337
(0x03000000):Function = 'MtiImbTreeIteratorImpl::fetchData'
(0x03000000):Type = ''
(0x03000000):Name = ''
(0x03000000):Label = ''
(0x03000000):Catalog = 'BIPv600'
(0x03000000):Severity = 3
(0x03000000):Number = 5341
(0x03000000):Text = 'Syntax Error: Unknown or Invalide Type found in Tree.'
I've tried checking the nillable attribute of the field and have played with the Encoding Numeric Null and Encoding Non-Numeric Null attributes of the message set and have had no luck. Any suggestions would be greatly appreciated. |
Typical reason here: Right tag wrong namespace.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| madi |
| Posted: Fri Nov 10, 2006 7:21 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
Hi All
I have this same error thats posted in this topic
i want to see if there is anything i could do yo prevent it or go around it
this is my flow
HTTPInput(MRM) --> AuthentcationSubflow -->Error Filter --> Conpute(MRM) --> HTTPReply
Authentication Subflow calls a service with the authentication details from the http headers which goes to a database to validate the user
now this flow was working fine until yesterday when i changed something in my Auth subflow.
what i changed has to do with the way i call the service inside the subflow
the message going in and out of the subflow is the same
but now i get this error
| Quote: |
( BROKER25.Interface16 ) An IMB syntax node Type Error has occurred during writing.
MtiImbSyntax Error: Unknown or Invalid Type found in IMB Tree. A call to getData() on a MtiImbSyntaxElement has found a type associated with an ImbValue which it cannot handle. This is an internal error.
Gather trace logs and contact support detailing what operations were performed. Examine any ESQL to see what type of manipulation occurred on elements. Review further error messages for an indication to the cause of the errors.
( BROKER25.Interface16 ) Message Translation Interface Writing Errors have occurred:
Message Set Name : ''RetrieveClientDetails''
Message Set Level : '1'
Message Format : ''XML1''
Message Type Path : ''Envelope''
Review further error messages for an indication to the cause of the errors. |
i cannot see how the changes in the subflow can effect the main flow especially when i have not touched the message ...... i just deal with the envronment i the suflow!!
if this is indeed a bug when does it show up and why??
--madi |
|
| Back to top |
|
|
| madi |
| Posted: Fri Nov 10, 2006 9:14 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
ok after many trail and error i could pin point where hte error is coming from
in the subflow im calling a service
Input --> Load properties --> Compute(prepare request message) --> HTTP Request --> Compute (to handle response) --> Out
this error occurs if i use XMLNSC parser for the response from HTTP Request Node (default --> message domain)
if i change it to XML or XMLNS the main flow is working fine ...... don't know why the domain here would effect the main flow 
the problem now is if I use the XML or XMLNS domains its not parsing correctly and if i use the xmlnsc parser which is parsing correctly but this MRM bug is getting triggered.
please let me know if there is a solution for this
--madi |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Nov 13, 2006 4:48 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
This error occurs if i use XMLNSC parser for the response from HTTP Request Node (default --> message domain)
if i change it to XML or XMLNS the main flow is working fine ...... don't know why the domain here would affect the main flow |
The message tree built by XMLNSC is different from the message tree built by XMLNS. That's the whole point of the XMLNSC domain - it builds compact trees which are faster to build, faster to access, and consume less memory.
To answer your question, I believe you are hitting a known defect when copying from an XML tree to an MRM tree. Installing FP3 may well fix it ( see IY88105 ) |
|
| Back to top |
|
|
| madi |
| Posted: Mon Nov 13, 2006 7:51 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
| Quote: |
| The message tree built by XMLNSC is different from the message tree built by XMLNS. That's the whole point of the XMLNSC domain - it builds compact trees which are faster to build, faster to access, and consume less memory. |
i kinda got that part ........ my point was the "known bug" is getting triggered only if i use XMLNSC parser
looks like FP3 is the answer
thanks kimbert
--madi |
|
| Back to top |
|
|
|
|
