| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Transformation Problem from CWF to XML |
« View previous topic :: View next topic » |
| Author |
Message
|
| satyasheel15 |
 Posted: Fri May 14, 2004 11:14 am Post subject: Message Transformation Problem from CWF to XML |
 |
|
Voyager
Joined: 04 Mar 2003
Posts: 86
|
Question:
We are truing to convert one CWF to XML. We have created one sample CWF message set with only two elemet :
Name and Age
The length of Name is 4 and of Age is 2.
We have created another message set XML with two same elements i.e.
Name and Age.
In the message flow, there is one MQInput Node where we have entered the properties of CWF and this is wired to Compute Node.
We have written the following code in the compute node to convert the CWF to XML:
___________________________________________________________
DECLARE I INTEGER;
SET I = 1;
WHILE I < CARDINALITY(InputRoot.*[]) DO
SET OutputRoot.*[I] = InputRoot.*[I];
SET I=I+1;
END WHILE;
SET "OutputRoot"."MRM"."Name" = "InputBody"."Name";
SET "OutputRoot"."MRM"."Age" = "InputBody"."Age";
SET OutputRoot.Properties.MessageSet = 'E18KE7S076001';
SET OutputRoot.Properties.MessageType = 'm_XMLEmp';
-- Enter SQL below this line. SQL above this line might be regenerated, causing any modifications to be lost.
SET OutputRoot.Properties.MessageFormat = 'XML1';
SET OutputRoot.Properties.MessageDomain = 'MRM';
___________________________________________________________
We are sending the following trace file which we had generated:-
___________________________________________________________
Timestamps are formatted in local time, 420 minutes before GMT.
2004-05-13 10:05:46.897998 3940 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node node 'testMsgFlow.MQInput1'.
2004-05-13 10:05:46.897998 3940 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'testMsgFlow.MQInput1' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-05-13 10:05:46.897998 3940 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'testMsgFlow.MQInput1' 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-05-13 10:05:47.118000 3940 UserTrace BIP6061I: Parser type 'MRM' created on behalf of node 'testMsgFlow.MQInput1' to handle portion of incoming message of length '6' bytes beginning at offset '364'. Parser type selected based on value 'MRM' from previous parser.
2004-05-13 10:05:47.118000 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'DECLARE I INTEGER;' at (1, 1).
2004-05-13 10:05:47.118000 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET I = 1;' at (2, 1).
2004-05-13 10:05:47.147998 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'WHILE I < CARDINALITY(InputRoot.*[ ]) DO ... END WHILE;' at (3, 1).
2004-05-13 10:05:47.147998 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (3, 7).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2540I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11). The result was '3'.
2004-05-13 10:05:47.158000 3940 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7). This resolved to '1 < 3'. The result was 'TRUE'.
2004-05-13 10:05:47.158000 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.*[I] = InputRoot.*[I];' at (4, 2).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputRoot.*[I]' at (4, 24).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 36).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 19).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputRoot.*[I]' to 'OutputRoot.*'.
2004-05-13 10:05:47.158000 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET I = I + 1;' at (5, 2).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I + 1' at (5, 9).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (5,  .
2004-05-13 10:05:47.158000 3940 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I + 1' at (5, 9). This resolved to '1 + 1'. The result was '2'.
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (3, 7).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2540I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11). The result was '3'.
2004-05-13 10:05:47.158000 3940 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7). This resolved to '2 < 3'. The result was 'TRUE'.
2004-05-13 10:05:47.158000 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.*[I] = InputRoot.*[I];' at (4, 2).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputRoot.*[I]' at (4, 24).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 36).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 19).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 19).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputRoot.*[I]' to 'OutputRoot.*'.
2004-05-13 10:05:47.158000 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET I = I + 1;' at (5, 2).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I + 1' at (5, 9).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (5, .
2004-05-13 10:05:47.158000 3940 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I + 1' at (5, 9). This resolved to '2 + 1'. The result was '3'.
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (3, 7).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2540I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11). The result was '3'.
2004-05-13 10:05:47.158000 3940 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7). This resolved to '3 < 3'. The result was 'FALSE'.
2004-05-13 10:05:47.158000 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.MRM = InputBody.Name;' at (7, 1).
2004-05-13 10:05:47.158000 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputBody.Name' at (7, 26).
2004-05-13 10:05:47.167999 3940 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputBody.Name' to 'OutputRoot.MRM'.
2004-05-13 10:05:47.167999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.MRM.Name = InputBody.Age;' at (8, 1).
2004-05-13 10:05:47.167999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputBody.Age' at (8, 33).
2004-05-13 10:05:47.167999 3940 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputBody.Age' to 'OutputRoot.MRM.Name'.
2004-05-13 10:05:47.167999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageSet = 'E18KE7S076001';' at (9, 1).
2004-05-13 10:05:47.167999 3940 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''E18KE7S076001'' to field / variable 'OutputRoot.Properties.MessageSet'.
2004-05-13 10:05:47.167999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageType = 'm_XMLEmp';' at (10, 1).
2004-05-13 10:05:47.167999 3940 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''m_XMLEmp'' to field / variable 'OutputRoot.Properties.MessageType'.
2004-05-13 10:05:47.167999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageFormat = 'XML1';' at (12, 1).
2004-05-13 10:05:47.167999 3940 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''XML1'' to field / variable 'OutputRoot.Properties.MessageFormat'.
2004-05-13 10:05:47.167999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageDomain = 'XML';' at (13, 1).
2004-05-13 10:05:47.167999 3940 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''XML'' to field / variable 'OutputRoot.Properties.MessageDomain'.
2004-05-13 10:05:47.167999 3940 UserTrace BIP4124I: Message propagated to 'out' terminal of compute node 'testMsgFlow.Compute1'.
2004-05-13 10:05:47.167999 3940 Error BIP2628E: Exception condition detected on input node 'testMsgFlow.MQInput1'.
The input node 'testMsgFlow.MQInput1' 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-05-13 10:05:47.167999 3940 RecoverableException BIP2230E: Error detected whilst processing a message in node 'testMsgFlow.MQOutput3'.
The message broker detected an error whilst processing a message in node 'testMsgFlow.MQOutput3'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2004-05-13 10:05:47.167999 3940 ParserException BIP5313E: Resource Manager: Message Format '{3}' does not match a Wire Format Descriptor or a Format Name.
This means that that either the message format had not been specified properly, a WFD resource has not been deployed, there is no Wire Format Descriptor '{3}' associated with message set '{2}', the installation is not valid (corrupted or incomplete) or that an unknown bitstream worker has been requested at resource registration time or at run time.
The Message Format can be either a Wire Format Identifier which identifies a descriptor associated with a particular message set or a Format Name which identifies a bistream worker. Redeploy the dictionary and check the control centres log. If the Message Format refers to a particular Wire Format Descriptor, ensure that the Message Format matches the correct Wire Format Identifier. If the Message Format refers to a particular bitstream worker, check that the appropriate bitstream worker file (dll or shared object) exists in the correct directory. E.g. On NT if we send an XML message to the broker we should have the file bipxmlworker.wrk in the <MQSI dir>bin directory. Other platforms should have the .wrk files in the <MQSI dir>/lib directory. Ensure that all the required workers are available and have loaded without error. The following workers should be available xml, pdf, cwf and tds.
2004-05-13 10:05:48.168998 3940 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'testMsgFlow.MQInput1'.
Node 'testMsgFlow.MQInput1' 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 MQSeries 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-05-13 10:05:48.168998 3940 UserTrace BIP2638I: The MQ output node 'testMsgFlow.MQOutput1' attempted to write a message to the specified queue 'in_fail' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 10:05:48.168998 3940 UserTrace BIP2622I: Message successfully output by MQ output node 'testMsgFlow.MQOutput1' to queue 'in_fail' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 10:10:04.487999 3940 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node node 'testMsgFlow.MQInput1'.
2004-05-13 10:10:04.487999 3940 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'testMsgFlow.MQInput1' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-05-13 10:10:04.487999 3940 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'testMsgFlow.MQInput1' 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-05-13 10:10:04.487999 3940 UserTrace BIP6061I: Parser type 'MRM' created on behalf of node 'testMsgFlow.MQInput1' to handle portion of incoming message of length '6' bytes beginning at offset '364'. Parser type selected based on value 'MRM' from previous parser.
2004-05-13 10:10:04.487999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'DECLARE I INTEGER;' at (1, 1).
2004-05-13 10:10:04.487999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET I = 1;' at (2, 1).
2004-05-13 10:10:04.487999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'WHILE I < CARDINALITY(InputRoot.*[ ]) DO ... END WHILE;' at (3, 1).
2004-05-13 10:10:04.487999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7).
2004-05-13 10:10:04.487999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (3, 7).
2004-05-13 10:10:04.487999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2540I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11). The result was '3'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7). This resolved to '1 < 3'. The result was 'TRUE'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.*[I] = InputRoot.*[I];' at (4, 2).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputRoot.*[I]' at (4, 24).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 36).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 19).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputRoot.*[I]' to 'OutputRoot.*'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET I = I + 1;' at (5, 2).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I + 1' at (5, 9).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (5, .
2004-05-13 10:10:04.527999 3940 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I + 1' at (5, 9). This resolved to '1 + 1'. The result was '2'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (3, 7).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2540I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11). The result was '3'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7). This resolved to '2 < 3'. The result was 'TRUE'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.*[I] = InputRoot.*[I];' at (4, 2).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputRoot.*[I]' at (4, 24).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 36).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 19).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 19).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputRoot.*[I]' to 'OutputRoot.*'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET I = I + 1;' at (5, 2).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I + 1' at (5, 9).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (5, .
2004-05-13 10:10:04.527999 3940 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I + 1' at (5, 9). This resolved to '2 + 1'. The result was '3'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (3, 7).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2540I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11). The result was '3'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7). This resolved to '3 < 3'. The result was 'FALSE'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.MRM = InputBody.Name;' at (7, 1).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputBody.Name' at (7, 26).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputBody.Name' to 'OutputRoot.MRM'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.MRM.Name = InputBody.Age;' at (8, 1).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputBody.Age' at (8, 33).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputBody.Age' to 'OutputRoot.MRM.Name'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageSet = 'E18KE7S076001';' at (9, 1).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''E18KE7S076001'' to field / variable 'OutputRoot.Properties.MessageSet'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageType = 'm_XMLEmp';' at (10, 1).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''m_XMLEmp'' to field / variable 'OutputRoot.Properties.MessageType'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageFormat = 'XML1';' at (12, 1).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''XML1'' to field / variable 'OutputRoot.Properties.MessageFormat'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageDomain = 'XML';' at (13, 1).
2004-05-13 10:10:04.527999 3940 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''XML'' to field / variable 'OutputRoot.Properties.MessageDomain'.
2004-05-13 10:10:04.527999 3940 UserTrace BIP4124I: Message propagated to 'out' terminal of compute node 'testMsgFlow.Compute1'.
2004-05-13 10:10:04.527999 3940 Error BIP2628E: Exception condition detected on input node 'testMsgFlow.MQInput1'.
The input node 'testMsgFlow.MQInput1' 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-05-13 10:10:04.527999 3940 RecoverableException BIP2230E: Error detected whilst processing a message in node 'testMsgFlow.MQOutput3'.
The message broker detected an error whilst processing a message in node 'testMsgFlow.MQOutput3'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2004-05-13 10:10:04.527999 3940 ParserException BIP5313E: Resource Manager: Message Format '{3}' does not match a Wire Format Descriptor or a Format Name.
This means that that either the message format had not been specified properly, a WFD resource has not been deployed, there is no Wire Format Descriptor '{3}' associated with message set '{2}', the installation is not valid (corrupted or incomplete) or that an unknown bitstream worker has been requested at resource registration time or at run time.
The Message Format can be either a Wire Format Identifier which identifies a descriptor associated with a particular message set or a Format Name which identifies a bistream worker. Redeploy the dictionary and check the control centres log. If the Message Format refers to a particular Wire Format Descriptor, ensure that the Message Format matches the correct Wire Format Identifier. If the Message Format refers to a particular bitstream worker, check that the appropriate bitstream worker file (dll or shared object) exists in the correct directory. E.g. On NT if we send an XML message to the broker we should have the file bipxmlworker.wrk in the <MQSI dir>bin directory. Other platforms should have the .wrk files in the <MQSI dir>/lib directory. Ensure that all the required workers are available and have loaded without error. The following workers should be available xml, pdf, cwf and tds.
2004-05-13 10:10:05.579999 3940 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'testMsgFlow.MQInput1'.
Node 'testMsgFlow.MQInput1' 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 MQSeries 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-05-13 10:10:05.579999 3940 UserTrace BIP2638I: The MQ output node 'testMsgFlow.MQOutput1' attempted to write a message to the specified queue 'in_fail' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 10:10:05.579999 3940 UserTrace BIP2622I: Message successfully output by MQ output node 'testMsgFlow.MQOutput1' to queue 'in_fail' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 10:16:33.277000 396 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node node 'testMsgFlow.MQInput1'.
2004-05-13 10:16:33.277000 396 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'testMsgFlow.MQInput1' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-05-13 10:16:33.277000 396 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'testMsgFlow.MQInput1' 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-05-13 10:16:33.798000 396 UserTrace BIP6061I: Parser type 'MRM' created on behalf of node 'testMsgFlow.MQInput1' to handle portion of incoming message of length '6' bytes beginning at offset '364'. Parser type selected based on value 'MRM' from previous parser.
2004-05-13 10:16:33.798000 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'DECLARE I INTEGER;' at (1, 1).
2004-05-13 10:16:33.798000 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET I = 1;' at (2, 1).
2004-05-13 10:16:33.798000 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'WHILE I < CARDINALITY(InputRoot.*[ ]) DO ... END WHILE;' at (3, 1).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (3, 7).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11).
2004-05-13 10:16:33.798000 396 UserTrace BIP2540I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11). The result was '3'.
2004-05-13 10:16:33.798000 396 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7). This resolved to '1 < 3'. The result was 'TRUE'.
2004-05-13 10:16:33.798000 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.*[I] = InputRoot.*[I];' at (4, 2).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputRoot.*[I]' at (4, 24).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 36).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 19).
2004-05-13 10:16:33.798000 396 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputRoot.*[I]' to 'OutputRoot.*'.
2004-05-13 10:16:33.798000 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET I = I + 1;' at (5, 2).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I + 1' at (5, 9).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (5, .
2004-05-13 10:16:33.798000 396 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I + 1' at (5, 9). This resolved to '1 + 1'. The result was '2'.
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (3, 7).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11).
2004-05-13 10:16:33.798000 396 UserTrace BIP2540I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11). The result was '3'.
2004-05-13 10:16:33.798000 396 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7). This resolved to '2 < 3'. The result was 'TRUE'.
2004-05-13 10:16:33.798000 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.*[I] = InputRoot.*[I];' at (4, 2).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputRoot.*[I]' at (4, 24).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 36).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 19).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (4, 19).
2004-05-13 10:16:33.798000 396 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputRoot.*[I]' to 'OutputRoot.*'.
2004-05-13 10:16:33.798000 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET I = I + 1;' at (5, 2).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I + 1' at (5, 9).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (5, .
2004-05-13 10:16:33.798000 396 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I + 1' at (5, 9). This resolved to '2 + 1'. The result was '3'.
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'I' at (3, 7).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11).
2004-05-13 10:16:33.798000 396 UserTrace BIP2540I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'CARDINALITY(InputRoot.*[ ])' at (3, 11). The result was '3'.
2004-05-13 10:16:33.798000 396 UserTrace BIP2539I: Node 'testMsgFlow.Compute1': Finished evaluating expression 'I < CARDINALITY(InputRoot.*[ ])' at (3, 7). This resolved to '3 < 3'. The result was 'FALSE'.
2004-05-13 10:16:33.798000 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.MRM.Name = InputBody.Name;' at (7, 1).
2004-05-13 10:16:33.798000 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputBody.Name' at (7, 33).
2004-05-13 10:16:33.807998 396 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputBody.Name' to 'OutputRoot.MRM.Name'.
2004-05-13 10:16:33.807998 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.MRM.Age = InputBody.Age;' at (8, 1).
2004-05-13 10:16:33.807998 396 UserTrace BIP2538I: Node 'testMsgFlow.Compute1': Evaluating expression 'InputBody.Age' at (8, 32).
2004-05-13 10:16:33.807998 396 UserTrace BIP2568I: Node 'testMsgFlow.Compute1': Performing tree copy of 'InputBody.Age' to 'OutputRoot.MRM.Age'.
2004-05-13 10:16:33.807998 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageSet = 'E18KE7S076001';' at (9, 1).
2004-05-13 10:16:33.807998 396 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''E18KE7S076001'' to field / variable 'OutputRoot.Properties.MessageSet'.
2004-05-13 10:16:33.807998 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageType = 'm_XMLEmp';' at (10, 1).
2004-05-13 10:16:33.807998 396 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''m_XMLEmp'' to field / variable 'OutputRoot.Properties.MessageType'.
2004-05-13 10:16:33.807998 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageDomain = 'XML';' at (12, 1).
2004-05-13 10:16:33.807998 396 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''XML'' to field / variable 'OutputRoot.Properties.MessageDomain'.
2004-05-13 10:16:33.807998 396 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageFormat = 'XML1';' at (13, 1).
2004-05-13 10:16:33.807998 396 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''XML1'' to field / variable 'OutputRoot.Properties.MessageFormat'.
2004-05-13 10:16:33.807998 396 UserTrace BIP4124I: Message propagated to 'out' terminal of compute node 'testMsgFlow.Compute1'.
2004-05-13 10:16:33.807998 396 Error BIP2628E: Exception condition detected on input node 'testMsgFlow.MQInput1'.
The input node 'testMsgFlow.MQInput1' 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-05-13 10:16:33.807998 396 RecoverableException BIP2230E: Error detected whilst processing a message in node 'testMsgFlow.MQOutput3'.
The message broker detected an error whilst processing a message in node 'testMsgFlow.MQOutput3'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2004-05-13 10:16:33.807998 396 ParserException BIP5313E: Resource Manager: Message Format '{3}' does not match a Wire Format Descriptor or a Format Name.
This means that that either the message format had not been specified properly, a WFD resource has not been deployed, there is no Wire Format Descriptor '{3}' associated with message set '{2}', the installation is not valid (corrupted or incomplete) or that an unknown bitstream worker has been requested at resource registration time or at run time.
The Message Format can be either a Wire Format Identifier which identifies a descriptor associated with a particular message set or a Format Name which identifies a bistream worker. Redeploy the dictionary and check the control centres log. If the Message Format refers to a particular Wire Format Descriptor, ensure that the Message Format matches the correct Wire Format Identifier. If the Message Format refers to a particular bitstream worker, check that the appropriate bitstream worker file (dll or shared object) exists in the correct directory. E.g. On NT if we send an XML message to the broker we should have the file bipxmlworker.wrk in the <MQSI dir>bin directory. Other platforms should have the .wrk files in the <MQSI dir>/lib directory. Ensure that all the required workers are available and have loaded without error. The following workers should be available xml, pdf, cwf and tds.
2004-05-13 10:16:34.808998 396 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'testMsgFlow.MQInput1'.
Node 'testMsgFlow.MQInput1' 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 MQSeries 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-05-13 10:16:34.808998 396 UserTrace BIP2638I: The MQ output node 'testMsgFlow.MQOutput1' attempted to write a message to the specified queue 'in_fail' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 10:16:34.808998 396 UserTrace BIP2622I: Message successfully output by MQ output node 'testMsgFlow.MQOutput1' to queue 'in_fail' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 10:29:01.513000 2492 UserTrace BIP4040I: The Execution Group 'default' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-05-13 10:29:01.513000 2492 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 10:29:01.513000 2492 UserTrace BIP2622I: Message successfully output by MQ output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 10:41:31.381000 2492 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node node 'ConfigurationMessageFlow.InputNode'.
2004-05-13 10:41:31.381000 2492 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-05-13 10:41:31.381000 2492 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' 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-05-13 10:41:31.381000 2492 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '15413' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-05-13 10:41:33.133998 2492 UserTrace BIP2267I: Message flow 'testMsgFlow' (uuid='aeb12a7b-fc00-0000-0080-ff19c3ea975d') successfully deleted.
The message broker received a configuration message containing an instruction to delete the message flow 'testMsgFlow' (uuid='aeb12a7b-fc00-0000-0080-ff19c3ea975d'), and successfully performed this action.
No user action required.
2004-05-13 10:41:33.183998 2492 UserTrace BIP2264I: Message flow 'testMsgFlow' (uuid='aeb12a7b-fc00-0000-0080-ff19c3ea975d') successfully created.
The message broker received a configuration message containing an instruction to create the message flow 'testMsgFlow' (uuid='aeb12a7b-fc00-0000-0080-ff19c3ea975d'), and successfully performed this action.
No user action required.
2004-05-13 10:41:33.214000 2492 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-05-13 10:41:33.234001 2492 UserTrace BIP7081I: The Publication Node has matched 0 subscriptions to topic '$SYS/Broker/MQSI_SAMPLE_BROKER/Configuration/ExecutionGroup/default' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-05-13 10:41:33.234001 2492 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-05-13 10:41:33.234001 2492 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-05-13 10:41:33.284000 2492 UserTrace BIP7082I: Node '': Publishing to destination MQSI_SAMPLE_QM:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233 for user mqsiuid.
A publication destination is being added to the list of destinations to MQSI_SAMPLE_QM:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233 for user mqsiuid.
No user action required.
2004-05-13 10:41:33.284000 2492 UserTrace BIP7081I: The Publication Node has matched 1 subscriptions to topic '$SYS/Broker/MQSI_SAMPLE_BROKER/Status/ExecutionGroup/default' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-05-13 10:41:33.284000 2492 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-05-13 10:41:33.293998 2492 UserTrace BIP2638I: The MQ output node 'PubSubControlMsgFlow.ListOutputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.ADMIN.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 10:41:33.293998 2492 UserTrace BIP2622I: Message successfully output by MQ output node 'PubSubControlMsgFlow.ListOutputNode' to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 10:41:33.293998 2492 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-05-13 10:41:33.293998 2492 UserTrace BIP7081I: The Publication Node has matched 0 subscriptions to topic '$SYS/Broker/MQSI_SAMPLE_BROKER/Configuration/ExecutionGroup/default' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-05-13 10:41:33.293998 2492 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-05-13 10:41:33.293998 2492 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-05-13 10:41:33.293998 2492 UserTrace BIP7082I: Node '': Publishing to destination MQSI_SAMPLE_QM:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233 for user mqsiuid.
A publication destination is being added to the list of destinations to MQSI_SAMPLE_QM:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233 for user mqsiuid.
No user action required.
2004-05-13 10:41:33.293998 2492 UserTrace BIP7081I: The Publication Node has matched 1 subscriptions to topic '$SYS/Broker/MQSI_SAMPLE_BROKER/Status/ExecutionGroup/default' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-05-13 10:41:33.293998 2492 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-05-13 10:41:33.293998 2492 UserTrace BIP2638I: The MQ output node 'PubSubControlMsgFlow.ListOutputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.ADMIN.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 10:41:33.293998 2492 UserTrace BIP2622I: Message successfully output by MQ output node 'PubSubControlMsgFlow.ListOutputNode' to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 10:41:33.493999 2492 UserTrace BIP4040I: The Execution Group 'default' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-05-13 10:41:33.493999 2492 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 10:41:33.493999 2492 UserTrace BIP2622I: Message successfully output by MQ output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 10:41:34.334999 2492 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node node 'ConfigurationMessageFlow.InputNode'.
2004-05-13 10:41:34.334999 2492 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-05-13 10:41:34.334999 2492 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' 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-05-13 10:41:34.334999 2492 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '173' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-05-13 10:41:34.334999 2492 UserTrace BIP4040I: The Execution Group 'default' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-05-13 10:41:34.345001 2492 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 10:41:34.345001 2492 UserTrace BIP2622I: Message successfully output by MQ output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 10:41:34.345001 2492 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node node 'ConfigurationMessageFlow.InputNode'.
2004-05-13 10:41:34.345001 2492 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-05-13 10:41:34.345001 2492 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' 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-05-13 10:41:34.345001 2492 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '993' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-05-13 10:41:34.345001 2492 UserTrace BIP4040I: The Execution Group 'default' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-05-13 10:41:34.345001 2492 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 10:41:34.345001 2492 UserTrace BIP2622I: Message successfully output by MQ output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 10:41:57.007999 2492 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node node 'ConfigurationMessageFlow.InputNode'.
2004-05-13 10:41:57.007999 2492 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-05-13 10:41:57.007999 2492 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' 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-05-13 10:41:57.007999 2492 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '167' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-05-13 10:41:57.018001 2492 UserTrace BIP4040I: The Execution Group 'default' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-05-13 10:41:57.018001 2492 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 10:41:57.018001 2492 UserTrace BIP2622I: Message successfully output by MQ output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 11:39:05.558000 2492 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node node 'ConfigurationMessageFlow.InputNode'.
2004-05-13 11:39:05.558000 2492 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-05-13 11:39:05.558000 2492 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' 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-05-13 11:39:05.558000 2492 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '15413' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-05-13 11:39:10.725000 2492 UserTrace BIP2267I: Message flow 'testMsgFlow' (uuid='aeb12a7b-fc00-0000-0080-ff19c3ea975d') successfully deleted.
The message broker received a configuration message containing an instruction to delete the message flow 'testMsgFlow' (uuid='aeb12a7b-fc00-0000-0080-ff19c3ea975d'), and successfully performed this action.
No user action required.
2004-05-13 11:39:10.776000 2492 UserTrace BIP2264I: Message flow 'testMsgFlow' (uuid='aeb12a7b-fc00-0000-0080-ff19c3ea975d') successfully created.
The message broker received a configuration message containing an instruction to create the message flow 'testMsgFlow' (uuid='aeb12a7b-fc00-0000-0080-ff19c3ea975d'), and successfully performed this action.
No user action required.
2004-05-13 11:39:10.795999 2492 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-05-13 11:39:10.805999 2492 UserTrace BIP7081I: The Publication Node has matched 0 subscriptions to topic '$SYS/Broker/MQSI_SAMPLE_BROKER/Configuration/ExecutionGroup/default' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-05-13 11:39:10.805999 2492 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-05-13 11:39:10.805999 2492 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-05-13 11:39:10.805999 2492 UserTrace BIP7082I: Node '': Publishing to destination MQSI_SAMPLE_QM:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233 for user mqsiuid.
A publication destination is being added to the list of destinations to MQSI_SAMPLE_QM:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233 for user mqsiuid.
No user action required.
2004-05-13 11:39:10.805999 2492 UserTrace BIP7081I: The Publication Node has matched 1 subscriptions to topic '$SYS/Broker/MQSI_SAMPLE_BROKER/Status/ExecutionGroup/default' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-05-13 11:39:10.805999 2492 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-05-13 11:39:10.815999 2492 UserTrace BIP2638I: The MQ output node 'PubSubControlMsgFlow.ListOutputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.ADMIN.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 11:39:10.815999 2492 UserTrace BIP2622I: Message successfully output by MQ output node 'PubSubControlMsgFlow.ListOutputNode' to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 11:39:10.815999 2492 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-05-13 11:39:10.815999 2492 UserTrace BIP7081I: The Publication Node has matched 0 subscriptions to topic '$SYS/Broker/MQSI_SAMPLE_BROKER/Configuration/ExecutionGroup/default' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-05-13 11:39:10.815999 2492 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-05-13 11:39:10.815999 2492 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-05-13 11:39:10.826000 2492 UserTrace BIP7082I: Node '': Publishing to destination MQSI_SAMPLE_QM:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233 for user mqsiuid.
A publication destination is being added to the list of destinations to MQSI_SAMPLE_QM:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233 for user mqsiuid.
No user action required.
2004-05-13 11:39:10.826000 2492 UserTrace BIP7081I: The Publication Node has matched 1 subscriptions to topic '$SYS/Broker/MQSI_SAMPLE_BROKER/Status/ExecutionGroup/default' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-05-13 11:39:10.826000 2492 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-05-13 11:39:10.826000 2492 UserTrace BIP2638I: The MQ output node 'PubSubControlMsgFlow.ListOutputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.ADMIN.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 11:39:10.826000 2492 UserTrace BIP2622I: Message successfully output by MQ output node 'PubSubControlMsgFlow.ListOutputNode' to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
2004-05-13 11:39:10.996000 2492 UserTrace BIP4040I: The Execution Group 'default' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-05-13 11:39:10.996000 2492 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
2004-05-13 11:39:10.996000 2492 UserTrace BIP2622I: Message successfully output by MQ output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MQSI_SAMPL |
|
| Back to top |
|
 |
| wooda |
| Posted: Mon May 17, 2004 3:42 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
The ESQL code you posted does not appear to match the trace you sent.
The trace of the compute node contains ...
| Quote: |
2004-05-13 10:05:47.167999 3940 UserTrace BIP2537I: Node 'testMsgFlow.Compute1': Executing statement 'SET OutputRoot.Properties.MessageDomain = 'XML';' at (13, 1).
2004-05-13 10:05:47.167999 3940 UserTrace BIP2566I: Node 'testMsgFlow.Compute1': Assigning value ''XML'' to field / variable 'OutputRoot.Properties.MessageDomain'.
|
whereas you're sample code is setting the domain to MRM.
I would speculate that what is happening is that you are setting you're Set,Type and Format correctly. Then you set the domain to XML and so the Set,Type and Format get lost. Then you set elements in the MRM output tree so when the message is written we are back in MRM land with no Set,Type and Format info.
Answer : You don't need to set the Domain property in your ESQL. Just set the Set,Type and Format. The fact that you have an output MRM tree will cause the MRM to be used.
So remove the line of ESQL where you set the Domain. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
