See information about the latest product version
Processing bytes messages with JMS nodes
The default behavior of WebSphere® Message Broker when processing bytes messages can affect clients that are designed to use the readUTF() and writeUTF() methods. Construct an equivalent UTF bit stream by using a Compute node.
By default, WebSphere Message Broker processes bytes messages by using the readBytes() and writeBytes() JMS methods. By using these methods, the payload is written or read as a raw byte array. For the input message, the behavior is based on the serialization of the message tree; for the output message, the resulting bit stream is passed to the user-specified parser to construct a logical tree.
This behavior can affect clients that are designed to use the readUTF() and writeUTF() methods. A UTF string contains encoded length information as well as the raw bit stream. To construct an equivalent UTF bit stream that can be read by the readUTF() method, complete the following steps.