This topic contains sections marked as revised for this release

WebSphere Message Brokers
File: au16534_
Writer: Jane Brockbank

Task topic

This build: July 31, 2007 21:39:28

Resolving implementation problems when developing message flows

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

Messages are directed to the failure terminal of an MQInput node

Error message BIP2211 is issued in z/OS by the 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

Your XSLTransform node is not working after deployment and errors are issued indicating that the style sheet could not be processed

Output messages are not sent to expected destinations

You experience problems when sending a message to an HTTP node's URL

Error message BIP5347 is issued on AIX when you run a message flow that uses a message set

Error message BIP2130 is issued with code page value of -1 or -2

QoS1 and QoS2 SCADA messages are not being processed

Related concepts
Message flows overview
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:39:28

au16534_ This topic's URL is: