[
https://issues.apache.org/jira/browse/ARTEMIS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207244#comment-16207244
]
ASF GitHub Bot commented on ARTEMIS-1464:
-----------------------------------------
Github user gemmellr commented on the issue:
https://github.com/apache/activemq-artemis/pull/1590
The AMQP JMS mapping is in part around getting any different AMQP JMS
implementations behaving consistently with each other, it could as easily say
use amqp-value, or say use either. The JMS mapping/client also copes with
receiving either, see the recieving side mapping details later in the doc.
There is nothing wrong with the broker sending amqp-value sections, and
other clients might prefer that. It seems entirely unrelated to the actual
defect here, so I'd leave it the way it is, but even if it were changed I would
actually separate it out as its own specific change.
> Core to AMQP conversion BytesMessage corrupts bytes
> ---------------------------------------------------
>
> Key: ARTEMIS-1464
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1464
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0
> Reporter: Michael Andre Pearce
> Assignee: Michael Andre Pearce
> Fix For: 2.4.0
>
>
> When sending a Core JMS BytesMessage and consuming via AMQP , the byte array
> is corrupted, the sent byte[] != received byte[]
> byte length is not equal, it seems the bodybuffer length is not honoured
> during the conversion (which caters for buffer headers and other offsets)
> Also noted is that when AMQP producer the body is of AMQP type "Data" where
> as when using Core producer and the broker translates to AMQP the body
> becomes AMQP type "AmqpValue", this also seems like a miss-behaviour and
> possibly linked to the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
