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

ASF subversion and git services commented on ARTEMIS-770:
---------------------------------------------------------

Commit 62627bf2ee4789d8c019170fba0fcbf64a697a38 in activemq-artemis's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=62627bf ]

ARTEMIS-770 AMQP Message Transformer refactor

Refactor the AMQP Message transformers both for better performance and
also to fix a number of issues with the transformers creating inbound
and outbound messages with incorrectly mapped values or extra data
appended where it should not be.


> AMQP: Incorrect or inefficient transformation of AMQP Messages 
> ---------------------------------------------------------------
>
>                 Key: ARTEMIS-770
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-770
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 1.4.0
>            Reporter: Timothy Bish
>
> The AMQP Message Transformations done in the protocol module can at times 
> produces incorrect conversion are append additional data not present in the 
> original AMQP message.
> Some noted issues
> * The Message Format value is not preserved from the original delivery.
> * Message Headers are added to outbound messages where the original message 
> did not have any which adds unnecessary overhead.
> * Message Properties can be added to outbound messages where the original did 
> not have any which adds unnecessary overhead and is illegal as the properties 
> section is immutable in AMQP.
> * Additional Application Properties are applied to outbound messages which 
> are meant to be immutable.
> * Some internal properties from the core message are applied to the Message 
> Annotations unnecessarily adding overhead to the outbound message.
> * The outbound message can contain a body that differs from the inbound 
> version in some cases
> * Object serialization / deserialization is done on types from the incoming 
> message that are wrapped in an AmqpValue instead of falling back to native 
> encoding to preserve the original Message body value.  



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

Reply via email to