MQSeries.net :: View topic - Error with a migrated Flow from wmqi 2.1 to wbimb 5.0

psn · Posted: Sun Nov 09, 2003 8:46 am Post subject:

Hi,

I have migrate a first flow with the mqsimigratemsgflows and teing it on the WBIMB 5.0 Broker. The input message go direkt on the failure node from the MQInput Node with MQRC = 2110 . I have trace the flow :

UserTrace BIP2636E: Warning when receiving a message: MQGET returned MQCC=1, MQRC=2110; message flow node 'ITIP_COLLECTOR_01_04.IN'.
The message flow node 'ITIP_COLLECTOR_01_04.IN' received a message from a queue, but a warning was generated. The return and reason code from the MQGET operation are as displayed. The message will be propagated to the failure terminal of the node.
Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
2003-11-06 16:51:28.885692 4884 UserTrace BIP2637I: Message propagated to failure terminal; node 'ITIP_COLLECTOR_01_04.IN'.
Node 'ITIP_COLLECTOR_01_04.IN' has received a message, but a warning was received from the MQGET operation. 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 not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.
2003-11-06 16:51:28.885950 4884 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ITIP_COLLECTOR_01_04.IN' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2003-11-06 16:51:28.886505 4884 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ITIP_COLLECTOR_01_04.IN' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2003-11-06 16:51:28.886993 4884 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ITIP_COLLECTOR_01_04.IN' to handle portion of incoming message of length '4438' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.

Have anybody an idea ?

PSN