MQSeries.net :: View topic

javaforvivek · Posted: Thu Aug 05, 2004 7:13 am Post subject:

WBIMBv5 + CSD3
My Input Message is read from a CSV file as follows:
10000,FirstName1,LastName1 (pressed enter)
20000,FirstName2,LastName
My message flow contains an MQInput node, followed by a Compute Node and then an MQOutput Node.
My message set contains 2 message formats : TDS1 and XML1.
My compute node contains just 2 lines of ESQL code:

SET OutputRoot = InputRoot;
SET Output.Properties.MessageFormat = 'XML'; (I refered SWIFT_TO_XML sample which is provided with WBIMB installation

I am using RFHUtil tool to read the data from file and put it on the input queue of my message flow. The user trace of the flow is debug.
I get following user trace:
Timestamps are formatted in local time, 60 minutes past GMT.

2004-08-05 14:36:28.063638 1984 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'CSVTrial_MsgFlow.MQInput'.
2004-08-05 14:36:28.064073 1984 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'CSVTrial_MsgFlow.MQInput' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-08-05 14:36:28.064323 1984 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'CSVTrial_MsgFlow.MQInput' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-08-05 14:36:28.064474 1984 UserTrace BIP6061I: Parser type 'MRM' created on behalf of node 'CSVTrial_MsgFlow.MQInput' to handle portion of incoming message of length '62' bytes beginning at offset '364'. Parser type selected based on value 'MRM' from previous parser.
2004-08-05 14:36:28.064634 1984 UserTrace BIP2537I: Node 'CSVTrial_MsgFlow.Compute': Executing statement 'BEGIN ... END;' at (.CSVTrial_MsgFlow_Compute.Main, 2.2).
2004-08-05 14:36:28.064758 1984 UserTrace BIP2537I: Node 'CSVTrial_MsgFlow.Compute': Executing statement 'CALL CopyEntireMessage();' at (.CSVTrial_MsgFlow_Compute.Main, 4.4).
2004-08-05 14:36:28.064823 1984 UserTrace BIP2537I: Node 'CSVTrial_MsgFlow.Compute': Executing statement 'BEGIN ... END;' at (.CSVTrial_MsgFlow_Compute.CopyEntireMessage, 1.39).
2004-08-05 14:36:28.064908 1984 UserTrace BIP2537I: Node 'CSVTrial_MsgFlow.Compute': Executing statement 'SET OutputRoot = InputRoot;' at (.CSVTrial_MsgFlow_Compute.CopyEntireMessage, 2.3).
2004-08-05 14:36:28.064981 1984 UserTrace BIP2538I: Node 'CSVTrial_MsgFlow.Compute': Evaluating expression 'InputRoot' at (.CSVTrial_MsgFlow_Compute.CopyEntireMessage, 2.20).
2004-08-05 14:36:28.065057 1984 UserTrace BIP2568I: Node 'CSVTrial_MsgFlow.Compute': Performing tree copy of 'InputRoot' to 'OutputRoot'.
2004-08-05 14:36:28.065294 1984 UserTrace BIP2537I: Node 'CSVTrial_MsgFlow.Compute': Executing statement 'SET OutputRoot.Properties.MessageFormat = 'XML';' at (.CSVTrial_MsgFlow_Compute.CopyEntireMessage, 3.3).
2004-08-05 14:36:28.065387 1984 UserTrace BIP2566I: Node 'CSVTrial_MsgFlow.Compute': Assigning value ''XML'' to field / variable 'OutputRoot.Properties.MessageFormat'.
2004-08-05 14:36:28.065465 1984 UserTrace BIP2537I: Node 'CSVTrial_MsgFlow.Compute': Executing statement 'RETURN TRUE;' at (.CSVTrial_MsgFlow_Compute.Main, 5.3).
2004-08-05 14:36:28.065568 1984 UserTrace BIP4124I: Message propagated to 'out' terminal of compute node 'CSVTrial_MsgFlow.Compute'.
2004-08-05 14:36:28.120887 1984 Error BIP2628E: Exception condition detected on input node 'CSVTrial_MsgFlow.MQInput'.
The input node 'CSVTrial_MsgFlow.MQInput' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2004-08-05 14:36:28.120979 1984 RecoverableException BIP2230E: Error detected whilst processing a message in node 'CSVTrial_MsgFlow.MQOut'.
The message broker detected an error whilst processing a message in node 'CSVTrial_MsgFlow.MQOut'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2004-08-05 14:36:28.121034 1984 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred:
Message Set Name : 'CSVTrial_MsgSet'
Message Set Level : '1'
Message Format : 'TDS1'
Message Type Path : 'File'
Review further error messages for an indication to the cause of the errors.
2004-08-05 14:36:28.121078 1984 ParserException BIP5424S: No Message Id received in TDS Parser Initialization
The TDS worker is not receiving a proper Message Id parameter during initialization.
Ensure that the message identifier used in your message matches the message as defined in the Message Brokers Toolkit.
2004-08-05 14:36:29.121292 1984 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'CSVTrial_MsgFlow.MQInput'.
Node 'CSVTrial_MsgFlow.MQInput' has received a message which has previously been backed out because of a processing error in the message flow. The MQMD 'backoutCount' of the message exceeds (or equals) the 'backoutThreshold' defined for the WebSphere Business Integration input queue. The message broker is propagating the message to the failure terminal of the node.
Examine the other messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
2004-08-05 14:36:29.121700 1984 UserTrace BIP2638I: The MQ output node 'CSVTrial_MsgFlow.MQFailure' attempted to write a message to queue 'FAIL' connected to queue manager 'WBRK_QM'. The MQCC was '0' and the MQRC was '0'.
2004-08-05 14:36:29.122125 1984 UserTrace BIP2622I: Message successfully output by output node 'CSVTrial_MsgFlow.MQFailure' to queue 'FAIL' on queue manager 'WBRK_QM'.

Threads encountered in this trace:
1984
I checked in RFHUtil tool for message Id, it shows me somthing like this :