[
https://issues.apache.org/jira/browse/ARTEMIS-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535064#comment-16535064
]
ASF GitHub Bot commented on ARTEMIS-1941:
-----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/2174
ARTEMIS-1941 fix failing tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1941
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/2174.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2174
----
commit d5fbac040721eb035a0c70a2dc383c47eacf39cd
Author: Justin Bertram <jbertram@...>
Date: 2018-07-06T15:14:48Z
ARTEMIS-1941 fix failing tests
----
> 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, ~500KB
> default) 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)
