activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ARTEMIS-768) Broker delivers STOMP message with invalid payload when using core api ClientProducer
Date Tue, 04 Oct 2016 19:37:20 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15546383#comment-15546383
] 

clebert suconic edited comment on ARTEMIS-768 at 10/4/16 7:36 PM:
------------------------------------------------------------------

it was marked as 1.1.0? I would check on 1.4.0.


was (Author: clebertsuconic):
her marked as 1.1.0? I would check on 1.4.0.

> Broker delivers STOMP message with invalid payload when using core api ClientProducer
> -------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-768
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-768
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Stomp
>    Affects Versions: 1.1.0
>         Environment: Redhat Linux 2.6
>            Reporter: Ruben Cala
>            Assignee: Justin Bertram
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message