You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Michael Justin (JIRA)" <ji...@apache.org> on 2015/09/26 16:41:04 UTC

[jira] [Created] (ARTEMIS-234) STOMP text message frames

Michael Justin created ARTEMIS-234:
--------------------------------------

             Summary: STOMP text message frames 
                 Key: ARTEMIS-234
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-234
             Project: ActiveMQ Artemis
          Issue Type: Bug
          Components: Stomp
    Affects Versions: 1.1.0
         Environment: Windows 8, Java 8
            Reporter: Michael Justin


In Artemis 1.0.0, distinction between text and binary message was possible based on the content-length header as documented: "A Stomp client can check the presence of the content-length header to determine the type of the message body (String or bytes)."

With Artemis 1.1.0 the MESSAGE frame always includes the content-length header, so that the distiction is not possible:

SEND
destination:jms.queue.ExampleQueue


Test message

received:

MESSAGE
subscription:{B806BF9D-B761-419C-8645-BBE3AED5CAF8}
message-id:2147488964
destination:jms.queue.ExampleQueue
expires:0
redelivered:false
priority:4
timestamp:1443278118819
content-length:12


Test message



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