[
https://issues.apache.org/jira/browse/ARTEMIS-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516185#comment-16516185
]
Robbie Gemmell commented on ARTEMIS-1941:
-----------------------------------------
Note for anyone looking later, the test for ARTEMIS-1940 added in
https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;a=commit;h=ed2a18f1c49bc1f45a7978f01989fd4b253f0693
will require fixing when this issue stops being the case.
> broker changes AMQP body section type during 'Large' message handling
> ---------------------------------------------------------------------
>
> Key: ARTEMIS-1941
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1941
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.6.1
> Reporter: Robbie Gemmell
> Priority: Major
>
> When the broker receives AMQP messages it considers those over a certain size
> (currently the lower of journal file size and journal buffer size) to be a
> 'large' message. In its handling of these, the message is essentially
> converted internally to a Core message, and when sending the message to an
> AMQP consumer, essentially gets converted back. During investigation of and
> testing of ARTEMIS-1940 I noted that although my test sent in an AMQP Data
> body section and so that is what should come back out, I instead received an
> AMQP Value body section containing a binary value (with the same bytes).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
