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
ESQL
Mappings and message references
Execution
Trace
Appearance
Other

Your migrated message flow project contains .msgnode files

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

You get an error message in ESQL when you move a routine

The product hangs when pasting ESQL statements from Adobe Acrobat

You don't know how message flows handle the code page of ESQL files

You do not know the naming restrictions for ESQL procedures and functions

You get error message BIP5431

You have problems calling Java from ESQL

Resources referenced by the mapping file cannot be resolved

You get errors when importing table schemas into the Message Flow Mapping editor

You get warnings or errors for message references

This practice is beneficial because the passed reference supports content-assistance and validation for ESQL. The message type content properties open, or open defined are not used in validation, and the assumption is that this property is closed.

There is an ESQL editor preference that lets you choose to ignore message reference mismatches, or to have them reported as a warning or an error. By default, this type of problem is reported as a warning, so you can still deploy the message flow.

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

Task list does not update when you make corrections to your files

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