WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resolving problems when using messages
Use the advice given here to help you to resolve common problems that can arise when you use messages.
- A communication error is issued when you use the enqueue facility
- The enqueue facility is not picking up changes made to a message
- You do not know which header elements affect enqueue
- Enqueue message files are still listed after they have been deleted
- The ESQL transform of an XML message gives unexpected results
- An XML message loses carriage return characters
- The broker is unable to parse an XML message
- Unexpected characters are displayed when using the XSLTransform node on z/OS
- Error message BIP5004 is issued by the XMLNS parser
- Error message BIP5378 is issued by the MRM parser
- Error message BIP5005 is issued by the Compute node
- A message is propagated to the Failure terminal of a TimeoutControl node
- Message processing fails within a TimeoutNotification node
- An MRM CWF message is propagated to the Failure terminal
- Problems with XML attributes
- An MRM XML message exhibits unexpected behavior
- The MRM parser has failed to parse a message because two attributes have the same name
- You encounter problems when messages contain EBCDIC newline characters
- The MIME parser produces a runtime error while parsing a message
- Runtime errors are issued when you write a MIME message from the logical message tree
- Output message has an empty message body
- Output message has an invalid message body indicated by error message BIP5005, BIP5016, or BIP5017
- Error message BIP5651 is issued when receiving a SOAP with Attachments message from a WebSphere Application Server client
- WebSphere Application Server produces an error when receiving a SOAP with Attachments message
- java_lang_StackOverflowError on AIX when processing a message flow that contains Java nodes and uses Java 5
- Problems when using code page translation on HP-UX
A communication error is issued when you use the enqueue facility
- Scenario: You use the enqueue or dequeue tools to put a message on a queue, but an error message is issued indicating that a communication error has occurred with the queue manager name.
- Explanation: The WebSphere® MQ queue manager has not started.
- Solution: Restart the WebSphere MQ queue manager.
The enqueue facility is not picking up changes made to a message
You do not know which header elements affect enqueue
- Scenario: When using the Enqueue editor, the accounting token, correlation ID, group ID, and message ID in the message header do not seem to affect behavior.
- Explanation: These fields do not affect behavior because they are not serialized properly.
Enqueue message files are still listed after they have been deleted
- Scenario: Enqueue message files are still listed in the menu after they have been deleted.
- Explanation: Deleted enqueue files are not removed from the menu. Nothing happens if you selecting these files.
The ESQL transform of an XML message gives unexpected results
An XML message loses carriage return characters
The broker is unable to parse an XML message
- Scenario: You receive a large XML file and wrap it in a SOAP envelope to be passed to a .NET web service. The broker is unable to parse the XML message
- Explanation: The message that you receive is defined as UTF-8 but it contains UTF-16 characters, such as £. The presence of these characters causes a problem with the parser: the broker is unable to parse the XML message because it contains an invalid character.
- Solution: Force the coded character set ID (CCSID) to 1208 instead of the default 437.
Unexpected characters are displayed when using the XSLTransform node on z/OS
- Scenario: When using the XSLTransform node on z/OS®, all the uppercase Os that are in an XML file on the incoming message are changed to underscore characters.
- Explanation: The XSLTransform node input message must come in as ASCII for the transform to work correctly. The XSLTransform node does not work with XML or XSL data in EBCDIC code. Java™ assumes a conversion from EBCDIC 1047. WebSphere Message Broker then converts to EBCDIC 500, because the CCSID is set to 500. EBCDIC 1047 and EBCDIC 500 are similar. Only uppercase O, J, and Z are different. (J and Z are also converted incorrectly.) The conversions leave a string that is unreadable because it is really in ASCII. However, it does convert the O from an EBCDIC 1047 character to an EBCDIC 500 character.
- Solution: Change your program either to do a string assignment without any conversions, or specify that the string is in ASCII ISO-8859-1 (CCSID 819).
Error message BIP5004 is issued by the XMLNS parser
Error message BIP5378 is issued by the MRM parser
Error message BIP5005 is issued by the Compute node
A message is propagated to the Failure terminal of a TimeoutControl node
Message processing fails within a TimeoutNotification node
An MRM CWF message is propagated to the Failure terminal
- Scenario: Your MRM CWF message is propagated to a Failure terminal, and generates error messages BIP5285, BIP5125, and BIP5181 or messages BIP5285, BIP5125, and BIP5288.
- Explanation: These errors report an inconsistency between the length of the message being processed, and the length of the message that is defined in the message model.
- Solution: Ensure that the length of the message as defined in the CWF layer is accurate. Check and correct the definition.
Problems with XML attributes
XML tags are written where XML attributes are expected, and vice versa.
An MRM XML message exhibits unexpected behavior
The MRM parser has failed to parse a message because two attributes have the same name
- Scenario: Two attributes in different name spaces have identical names. Error message BIP5117 is issued.
- Explanation: The MRM parser has failed to parse the message.
- Solution: Modify the attribute names so that they are not identical. This problem is a known limitation with the parser.
You encounter problems when messages contain EBCDIC newline characters
The MIME parser produces a runtime error while parsing a message
Runtime errors are issued when you write a MIME message from the logical message tree
Output message has an empty message body
Output message has an invalid message body indicated by error message BIP5005, BIP5016, or BIP5017
Error message BIP5651 is issued when receiving a SOAP with Attachments message from a WebSphere Application Server client
WebSphere Application Server produces an error when receiving a SOAP with Attachments message
java_lang_StackOverflowError on AIX when processing a message flow that contains Java nodes and uses Java 5
Problems when using code page translation on HP-UX
- Scenario: You experience code page translation problems on HP-UX.
- Solution: Check the WebSphere MQ queue manager attribute CodedCharSetID. The default value for this attribute is 1051. Change this value to 819 for queue managers that host WebSphere Message Broker components.