| Author |
Message
|
| kirank |
 Posted: Fri Feb 24, 2006 10:05 am Post subject: XML transformation Node |
 |
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
Hi,
I am trying to use XML transformation node for transformation using a Stylesheet. I have specified all the properties of this node. But I am getting following error text in the error message. Has anybody seen this error?
<ErrorText> Node throwing exception. </ErrorText>
<ErrorText> Value not valid <com.ibm.broker.plugin.MbRecoverableException class:JNI method:ImbValue::checkValid source:BIPv500 key:2329 > <com.ibm.broker.plugin.MbRecoverableException class:JNI method:ImbValue::checkValid source:BIPv500 key:2329 > at com.ibm.broker.plugin.MbElement._getValue(Native Method) at com.ibm.broker.plugin.MbElement.getValue(MbElement.java:1161) at com.ibm.xsl.mqsi.XMLTransformNode.setOptionsFromPropertiesFolder(XMLTransformNode.java:1012) at com.ibm.xsl.mqsi.XMLTransformNode.evaluate(XMLTransformNode.java:857) . </ErrorText>
Thanks
Kiran |
|
| Back to top |
|
 |
| kirank |
| Posted: Fri Feb 24, 2006 4:04 pm Post subject: |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
In my previous post i had mentioned error text as reported by my error flow. After doing the trace I found that the error related to XML transformation node is
RecoverableException BIP2329E: An unexpected NULL value was encountered
I don't have any null values in my stylseheet or in the input message. Is there any other setting on this node that is causing this error?
Thanks
Kiran |
|
| Back to top |
|
|
| andypiper |
| Posted: Tue Feb 28, 2006 2:10 am Post subject: |
|
|
Acolyte
Joined: 29 Oct 2001
Posts: 59
Location: London
|
| Did you try enabling the detailed trace for the node itself? It might provide more clues. |
|
| Back to top |
|
|
| kirank |
| Posted: Tue Feb 28, 2006 8:35 am Post subject: |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
Haven't tried enabling trace for the node. How do you do that? Is it documented in any guide?
Also I am WBIMB 5.0 CSD 3 level. Am I missing any jar file that this version requires? I am getting only "RecoverableException BIP2329E: An unexpected NULL value was encountered" as error in the debug trace.
Thanks
Kiran |
|
| Back to top |
|
|
| kirank |
| Posted: Tue Feb 28, 2006 9:06 am Post subject: |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
I tried the trace option on the node properties and that did not give any additional trace. The trace only says
The message broker detected an error whilst processing a message in node 'GTMS_EAI_MAINFLOW.GNETID_XMLTransformation'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing. See the following messages for details of the error.
2006-02-28 08:59:53.556949 2580 RecoverableException BIP2329E: An unexpected NULL value was encountered
This message will be accompanied with others which will give the higher level context for this error. Look at these other messages to determine the root source of the problem.
I have checked the event log and there is nothing there. Am I missing anything?
Thanks
Kiran |
|
| Back to top |
|
|
| andypiper |
| Posted: Tue Feb 28, 2006 9:25 am Post subject: |
|
|
Acolyte
Joined: 29 Oct 2001
Posts: 59
Location: London
|
Are you sure? You should have a more detailed XML transformation log in the <broker workpath>\log directory, e.g. on Windows this is
C:\Documents and Settings\All Users\Application Data\IBM\MQSI\common\log\XMLTTrace.log |
|
| Back to top |
|
|
| kirank |
| Posted: Tue Feb 28, 2006 9:55 am Post subject: |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
I found the trace file. Here is what I get in XMLTTrace.log file. It is not clear exactly what is the error.
Do you see anything wrong here? I have all default values for properties of this node.
ConfigDirectory=/C:/WBIMB/bin
DefaultStylesheetLocation=C:/
TraceMask=262660
MessageLoggingEnabled=true
StylesheetSelectionPriority=2,1,
MaxStylesheetCacheEntries=5
MessageAndTraceGroupname=com.ibm.xsl.mqsi
Thread-10 Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLMQSINodeMessageLoggingHandler logRecord Message Type (String): TYPE_ERR TYPE_ERROR_EXC TYPE_MISC_DATA TYPE_LEVEL1 TYPE_LEVEL2 TYPE_LEVEL3
Thread-10 Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLMQSINodeMessageLoggingHandler logRecord Message Text : EnhancedXMLTransform Engine Initialization complete.
Thread-10 Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLMQSINodeMessageLoggingHandler logRecord Message Type (String): TYPE_ERR TYPE_ERROR_EXC TYPE_LEVEL1 TYPE_LEVEL2
Thread-10 Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLMQSINodeMessageLoggingHandler logRecord Message Text : Exit
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode evaluate set Trace Mask to ALL
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode evaluate Get Message Information
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode evaluate Set Message Options
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode setOptionsFromPropertiesFolder Entry
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode setOptionsFromPropertiesFolder Exit/Throwing
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode logXMLTransformException Entry
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode logXMLTransformException Class Name: com.ibm.xsl.mqsi.XMLTransformNode
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode logXMLTransformException Method Name: setOptionsFromPropertiesFolder
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode logXMLTransformException Message Source: BIPv500
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode logXMLTransformException Message Key: 2329
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode logXMLTransformException Other Info:
Value not valid
<com.ibm.broker.plugin.MbRecoverableException class:JNI method:ImbValue::checkValid source:BIPv500 key:2329 >
<com.ibm.broker.plugin.MbRecoverableException class:JNI method:ImbValue::checkValid source:BIPv500 key:2329 >
at com.ibm.broker.plugin.MbElement._getValue(Native Method)
at com.ibm.broker.plugin.MbElement.getValue(MbElement.java:1161)
at com.ibm.xsl.mqsi.XMLTransformNode.setOptionsFromPropertiesFolder(XMLTransformNode.java:1012)
at com.ibm.xsl.mqsi.XMLTransformNode.evaluate(XMLTransformNode.java:857)
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode logXMLTransformException Exit
GNETID_XMLTransformation Tue Feb 28 09:50:04 PST 2006 com.ibm.xsl.mqsi.XMLTransformNode evaluate Error - Find Failure Terminal
Thanks
Kiran |
|
| Back to top |
|
|
| andypiper |
| Posted: Wed Mar 01, 2006 3:40 am Post subject: |
|
|
Acolyte
Joined: 29 Oct 2001
Posts: 59
Location: London
|
| This suggests that perhaps you have set something in the message properties that is not valid. Can you tell us what you have set in the message Properties folder? |
|
| Back to top |
|
|
| kirank |
| Posted: Wed Mar 01, 2006 9:00 am Post subject: |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
I am not setting anything in message properties. After doing some more testing with it I found that I get that error when I use sub-flow containing XML transformation node. When I do a simple message flow with one input queue, XML transformation node and then output queue, I don't get any error and the transformation is fine. So using it as a sub-flow does something to message properties which XML transformation node does not like. Is that a known issue? I am at CSD level 3. Is it fixed in other CSD's? We can not do a upgrade right now so I will have to do away with Sub-flow if there is no way to get it working. Let me know if anyone has experienced it.
Thanks
Kiran |
|
| Back to top |
|
|
| kirank |
| Posted: Wed Mar 01, 2006 10:17 am Post subject: Solved |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
I found that there was another sub-flow before my flow that was wiping out message properties. That was causing the error as reported by XML trace. So there is no issue with using XML transformation node in sub-flows.
Thanks andypiper for your inputs.
Regards
Kiran |
|
| Back to top |
|
|
| andypiper |
| Posted: Wed Mar 01, 2006 12:43 pm Post subject: |
|
|
Acolyte
Joined: 29 Oct 2001
Posts: 59
Location: London
|
You're welcome. Don't forget to turn off the detailed trace from the XMLTransformation node now!  |
|
| Back to top |
|
|
|
|
