Problems when developing message flows

This section outlines some common problems that can arise when developing message flows. It contains advice for dealing with the problems:

Migration
Execution
Trace
Appearance
Other

You do not know whether you need to migrate the IBM primitives

Messages are directed to the failure terminal of an MQInput node

Messages enter the message flow but do not exit

Execution group is not reading messages from the input queues

DataFlowEngine terminates while processing messages

Start of change

Your execution group hangs or terminates with a core dump

End of change
Start of change

An aggregation flow appears to hang after processing a small number of messages under heavy load

End of change

You cannot determine which node is being referenced in your trace file

You cannot see any alerts when you change user trace

You rename a flow that contains errors, but the task list entries remain

Terminals on a subflow get out of sync as changes are made

The values of your promoted properties were lost after editing

You get an exception when saving changes to a .tblxmi file

You don't know when to use the MQeMbMsgObject

Start of change

QoS1 and QoS2 SCADA messages are not being processed

End of change