Resolving problems when developing message flows

This topic contains advice for dealing with some common problems that can arise when developing message flows:

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 Version 2.1 IBM primitives

A routine not defined error message is issued in ESQL when you move a routine

The product hangs when you paste ESQL statements from Adobe Acrobat

You do not know how message flows handle the code page of ESQL files

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

Error message BIP5431 is issued and the broker fails

You are unable to call Java from ESQL

Start of change

Error message BIP3203 is issued: Format expression is not a valid FORMAT expression for converting expression to type

End of change
Start of change

Error message BIP3204 is issued: Input expression does not match FORMAT expression Parsing failed to match

End of change
Start of change

Error message BIP3205 is issued: The use of a FORMAT expression is not allowed when converting

End of change

Resources that are referenced by the mapping file cannot be resolved

Errors are issued when you import table schemas into the Message Flow Mapping editor

Warnings or errors are issued 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 allows you to 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

Your execution group is not reading messages from the input queues

The DataFlowEngine terminates while processing messages

Your execution group hangs or terminates with a core dump

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

Output messages are not sent to expected destinations

QoS1 and QoS2 SCADA messages are not being processed

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

You cannot see any alerts when you change user trace

The 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 are lost after editing

Start of change

The Message Flow editor experiences problems when opening a message flow and opens in error mode

End of change

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

You do not know when to use the MQeMbMsgObject object

Related concepts
Message flows overview