[
https://issues.apache.org/jira/browse/ARTEMIS-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660779#comment-16660779
]
ASF subversion and git services commented on ARTEMIS-2096:
----------------------------------------------------------
Commit d72a7acbb7cdf842ab908a00cbecb8e2ca6b56e7 in activemq-artemis's branch
refs/heads/2.6.x from [~gaohoward]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=d72a7ac ]
ARTEMIS-2135 Test multiple core consumers receiving amqp messages
This test can verify an issue fixed by the commit:
7a463f038ae324f2c5c908321b2ebf03b5a8e303 (ARTEMIS-2096)
The issue was reported later by users where messages
sent by amqp clients are having their body size
randomly being zero when received by multiple core
consumers.
This was also fixed on commit 48e0fc8f42346d96bc809593a150e05a586787e but that
was exclusively on 2.6.x branch.
(cherry picked from commit f4c93a2860f384ce87e3589012e5278399c550c3)
> AMQP: Refactoring AMQPMessage abstraction for better consistency and
> performance
> --------------------------------------------------------------------------------
>
> Key: ARTEMIS-2096
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2096
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.6.3
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Major
> Fix For: 2.7.0
>
>
> The AMQPMessage abstraction used to wrap the AMQP message section has some
> inconsistencies in how it manages the underlying data and the decoded AMQP
> section obtained from the Proton-J codec as well as issues with state being
> maintained in the presence of changes to the message made through the public
> facing Message APIs
> A refactoring of the AMQPMessage class to better utilize the proton-j codec
> to manage the message data and how it is parsed and re-encoded on change
> needs to be done to ensure no corrupt messages are sent and that we are not
> decoding and encoding sections of the message we are not intending to read or
> change on the sever (We currently can decode message bodies or footer is a
> few cases where we intend not to).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
