MQSeries.net :: View topic - Message truncated after XML Transform node

gpkssts · Posted: Fri Aug 25, 2006 2:20 am Post subject:

(We are on Solaris WBIMB v5 CSD5)

In a very simple test flow we transform a CWF message to XML, push the results through the XML Transform node and then write the results to a queue.

With small messages we have no problems and it works just fine.

With larger (but kb not mb size) messages the results are truncated.

I'm getting no errors reported.

Here's what I've tried:

-enabling the nodes trace option - no obvious errors in there, you see the start of the message (with a message about only showing 1000 bytes so I assume thats normal), then these lines:

XMLTransformation Fri Aug 25 09:01:56 BST 2006 com.ibm.xsl.mqsi.MessageGenerator
createNewMessage Calling MbMessage.getRootElement()
XMLTransformation Fri Aug 25 09:01:56 BST 2006 com.ibm.xsl.mqsi.MessageGenerator
createNewMessage add new data with createElementAsLastChild
XMLTransformation Fri Aug 25 09:01:56 BST 2006 com.ibm.xsl.mqsi.MessageGenerator
createNewMessage find /Properties/CodedCharSetId
XMLTransformation Fri Aug 25 09:01:56 BST 2006 com.ibm.xsl.mqsi.MessageGenerator
createNewMessage Exit
XMLTransformation Fri Aug 25 09:01:56 BST 2006 com.ibm.xsl.mqsi.MessageGenerator
createNewMessageAssembly Entry
XMLTransformation Fri Aug 25 09:01:56 BST 2006 com.ibm.xsl.mqsi.MessageGenerator
createNewMessageAssembly Exit
XMLTransformation Fri Aug 25 09:01:56 BST 2006 com.ibm.xsl.mqsi.XMLTransformNode
evaluate Find Output Terminal
XMLTransformation Fri Aug 25 09:01:56 BST 2006 com.ibm.xsl.mqsi.XMLTransformNode
evaluate Propagate New Message
XMLTransformation Fri Aug 25 09:01:56 BST 2006 com.ibm.xsl.mqsi.XMLTransformNode
evaluate Exit

So I thought that looked ok.

-compared running the same flow on a windows broker but it worked fine there with no issues, same csd level

- tried running the conversion at a command line on the solaris box to look for any issues - I did this for that:

cd /opt/mqsi/jre/bin
./java -cp ../../classes/xalan.jar:../../classes/brokerXerces.jar org.apache.xalan.xslt.Process -IN ~/gp/aaproxy.xml -XSL ~/gp/SMISForm.xsl

-changing the jvm heap size from the default to 256 MB (desparation)
-restarted everything (EG, Broker) (more desparation - just in case!)

Not sure how the transform node does its thing. Its like a buffer isn't flushed before the flow moves on.

If it had been one of our developments I'd have wondered about the finalization of the output or some break down in a JNI layer but I'm stuck really.

I've seen some posts from other people talking about much larger XML files than ours in this node with no problems like this but it does seem to be related to size in our case.

Has anyone seen this before and got any advice or shall I just raise a PMR?

Thanks,

Graham