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

ASF GitHub Bot commented on ARTEMIS-2096:
-----------------------------------------

GitHub user gaohoward opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2383

    NO-JIRA Adding a test for ARTEMIS-2096

    This test can verify an issue fixed by the commit:
    7a463f038ae324f2c5c908321b2ebf03b5a8e303 (ARTEMIS-2096)
    The issue was reported in:
    https://issues.jboss.org/browse/ENTMQBR-2034
    but not reported in Artemis.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gaohoward/activemq-artemis c_2034

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/2383.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 #2383
    
----
commit 89ef072d80d6d034be73244af05617b2bf3baf36
Author: Howard Gao <howard.gao@...>
Date:   2018-10-19T13:40:33Z

    NO-JIRA Adding a test for ARTEMIS-2096
    
    This test can verify an issue fixed by the commit:
    7a463f038ae324f2c5c908321b2ebf03b5a8e303 (ARTEMIS-2096)
    The issue was reported in:
    https://issues.jboss.org/browse/ENTMQBR-2034
    but not reported in Artemis.

----


> 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)

Reply via email to