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


Resolving problems when using messages

Use the advice given here to help you to resolve common problems that can arise when you use messages.

About this task

Procedure

A communication error is issued when you use the enqueue facility

Procedure

The enqueue facility is not picking up changes made to a message

Procedure

You do not know which header elements affect enqueue

Procedure

Enqueue message files are still listed after they have been deleted

Procedure

The ESQL transform of an XML message gives unexpected results

Procedure

An XML message loses carriage return characters

Procedure

The integration node is unable to parse an XML message

Procedure

Unexpected characters are displayed when using the XSLTransform node on z/OS

Procedure

Error message BIP5004 is issued by the XMLNS parser

Procedure

Error message BIP5378 is issued by the MRM parser

Procedure

Error message BIP5005 is issued by the Compute node

Procedure

A message is propagated to the Failure terminal of a TimeoutControl node

Procedure

Message processing fails within a TimeoutNotification node

Procedure

An MRM CWF message is propagated to the Failure terminal

Procedure

Problems with XML attributes

About this task

XML tags are written where XML attributes are expected, and vice versa.

Procedure

An MRM XML message exhibits unexpected behavior

Procedure

The MRM parser has failed to parse a message because two attributes have the same name

Procedure

You encounter problems when messages contain EBCDIC newline characters

Procedure

The MIME parser produces a runtime error while parsing a message

Procedure

Runtime errors are issued when you write a MIME message from the logical message tree

Procedure

Output message has an empty message body

Procedure

Output message has an invalid message body indicated by error message BIP5005, BIP5016, or BIP5017

Procedure

Error message BIP5651 is issued when receiving a SOAP with Attachments message from a WebSphere Application Server client

Procedure

WebSphere Application Server produces an error when receiving a SOAP with Attachments message

Procedure

java_lang_StackOverflowError on AIX when processing a message flow that contains Java nodes and uses Java 5

Procedure

Problems when using code page translation on HP-UX

Procedure

Unable to access messages on a remote WebSphere MQ queue

Procedure

  • Scenario: Error message BIP2677 occurs when an MQInput node is attempting to access messages on a remote queue.
  • Explanation: This error can occur when an MQInput node is using the WebSphere MQ callback mechanism to receive messages from a queue.
  • Solution: Check the WebSphere MQ completion and reason codes in the WebSphere MQ product documentation to determine the cause of the error. If the error is MQ_ENVIRONMENT_ERROR (2012), a likely cause is that the SHARECNV (shared conversations) parameter for the connected channel is set to 0. To resolve the problem, ensure that the SHARECNV parameter for the channel is set to the default value of 10.

A WebSphere MQ message does not complete backout processing, and BackoutCount increments continuously

Procedure


au16550_.htm | Last updated 2015-03-27 19:27:30