IBM Integration Bus, Version 10.0.0.17 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Resolving implementation problems when developing message flows

Use the advice given here to help you to resolve some common problems that can arise when running message flows.

About this task

Messages are directed to the Failure terminal of an MQInput node

Procedure

Error message BIP2211 is issued on z/OS by the MQInput node

Procedure

Messages enter the message flow but do not exit

Procedure

Your integration server is not reading messages from the input queues

Procedure

The integration server ends while processing messages

About this task

Procedure

Your integration server hangs, or ends with a core dump

Procedure

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

Procedure

Output messages are not sent to expected destinations

Procedure

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

Procedure

When using secure HTTP connections, you change a DNS host's destination but the integration node is using a cached DNS host definition

Procedure

The TimeoutControl node issues error message BIP4606 or BIP4607 when the timeout request start time that it receives is in the past

Procedure

You are using a TimeoutControl node with a TimeoutNotification node, with multiple clients running concurrently, and messages appear to be being dropped

Procedure

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

About this task

Procedure

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

Procedure

The integration server restarts before an MQGet node has retrieved all messages

Procedure


au16534_.htm | Last updated 2019-07-13 08:13:13