Author |
Message
|
ravi_ishere |
Posted: Wed Feb 13, 2008 12:38 am Post subject: XML Parsing Exceptions when Applying XML Transformation |
|
|
Apprentice
Joined: 20 Jan 2008 Posts: 29
|
Hi,
I am facing an issue of xml parsing excception
Problem:
1. In a mesage flow two different sub flows using xml transformation nodes.with two different XSL files.
2. In the sequence first xml transformation is working fine and gettign the expected results. Second XML Transformation is giving exceptions in the Exception List.
3.If i removed the first subflow and retains the second subflow the transfomation is applying fine and geeting expected results with Both different xsl files above i mentioned.
4. I have noticed that when XML Transformation is applying in the same message flow i am getting theis exception.
5. I have checked the XML Transformation node priorities and XSL Files both are fine
Can anyone tell what is the why it is happening.
Here is the Eeception list i am getting :
CHARACTER Text = \n\nXML Writing Errors have occurred\n\n<com.ibm.broker.plugin.MbParserException class:JNI method:ImbGenericXmlParser::refreshBitStreamFromElements source:BIPv600 key:5010 >\n\n<com.ibm.broker.plugin.MbParserException class:JNI method:ImbGenericXmlParser::refreshBitStreamFromElements source:BIPv600 key:5010 >\r\n\tat com.ibm.broker.plugin.MbElement._toBitstream(Native Method)\r\n\tat com.ibm.broker.plugin.MbElement.toBitstream(MbElement.java:2221)\r\n\tat com.ibm.xsl.mqsi.XMLTransformData.extractDataFromMessage(XMLTransformData.java:193)\r\n\tat com.ibm.xsl.mqsi.XMLTransformNode.evaluate(XMLTransformNode.java:938)\r\n\tat com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1298)\r\n\tat com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)\r\n\tat com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:140)\r\n\tat com.ibm.xsl.mqsi.XMLTransformNode.evaluate(XMLTransformNode.java:1021)\r\n\tat com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1298)\r\n
Thanks
R |
|
Back to top |
|
 |
AJStar |
Posted: Wed Feb 13, 2008 2:27 am Post subject: |
|
|
 Acolyte
Joined: 27 Jun 2007 Posts: 64
|
Is the error thrown by the XML Transformation node or after the node?
Check if the output from the first XMLT node is the desired input to the second XMLT node. _________________ Regards
AJ |
|
Back to top |
|
 |
kimbert |
Posted: Wed Feb 13, 2008 2:39 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
- It is not an XML parsing error. It is an 'XML Writing Error'
- That is not the full exception list. It only contains the top-level XML writing exception reported by the XMLNSC parser. There will definitely be other exceptions in the list. Please insert a Trace node and trace the exception list. If the other exceptions appear in the trace output, please post them here.
- If you still cannot see the other exceptions, please take a user trace. It will definitely contain the full text of all exceptions. |
|
Back to top |
|
 |
ravi_ishere |
Posted: Wed Feb 13, 2008 3:19 am Post subject: |
|
|
Apprentice
Joined: 20 Jan 2008 Posts: 29
|
Exception what i posted here is got from Exceptionlist i saw in Debugger mode in WBI MB tool kit. For full trace of exception can i add Trace? |
|
Back to top |
|
 |
Vitor |
Posted: Wed Feb 13, 2008 3:22 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
ravi_ishere wrote: |
For full trace of exception can i add Trace? |
kimbert wrote: |
Please insert a Trace node and trace the exception list. If the other exceptions appear in the trace output, please post them here |
My 2 cents - I'd go straight to the user trace rather than a Trace node but that's just me. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
kimbert |
Posted: Wed Feb 13, 2008 3:33 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
|
Back to top |
|
 |
ravi_ishere |
Posted: Wed Feb 13, 2008 5:11 am Post subject: |
|
|
Apprentice
Joined: 20 Jan 2008 Posts: 29
|
Yes we have placed the trace but in it we are getting the same exception what i am posted. Any help on this. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Feb 13, 2008 5:21 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
ravi_ishere wrote: |
Yes we have placed the trace but in it we are getting the same exception what i am posted. |
We never said doing a trace would fix the problem, just help isolate it. There should be way more information in the trace than you've previously posted and it's this information which is crucial to solving your problem, as it explains what's actually happening!
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Feb 13, 2008 5:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Please post the trace. Post at least TEN (and no more than 20) lines BEFORE the exception and the same amount AFTER the exception. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
ravi_ishere |
Posted: Wed Feb 13, 2008 5:59 am Post subject: |
|
|
Apprentice
Joined: 20 Jan 2008 Posts: 29
|
Hi Thanks for youe inputs. When we are checking the trace it is showing that XML Writing Errors have occurred with the with all that i posted.
We are unsure that it may be the tool kit issue that running the XMLT in the flow two time sequentially. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Feb 13, 2008 6:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
We can't help you more until you either post the trace, or post much more information than you have. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
kimbert |
Posted: Wed Feb 13, 2008 6:13 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
hi ravi_ishere,
Have you used the command-line tools mqsichangetrace. mqsireadlog and mqsiformatlog? If you have not, please do so. |
|
Back to top |
|
 |
|