Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
1.1.0
-
None
-
None
-
Redhat Linux 2.6
Description
When using core api ClientProducer to publish messages with a text payload (xml string, btw) to the broker, the messages sent to stomp consumers have an invalid stomp body.
In the message delivered to stomp consumers, the original text payload was 5 characters longer than the published payload. The stomp messages delivered had 3 extra characters at the front of the payload, and 2 extra characters at the end (spaces), before the final terminating NULL character.
Besides the fact that the string payload is different from what was published, the 3 extra characters in the front of the stomp message often contained the NULL character.
This violates the stomp MESSAGE format, and was causing incorrect stomp message parsing.
The workaround for this was to use the stomp content-length header to determine how many bytes to read in for the body, then manually discarding the garbage characters.