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

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

GitHub user clebertsuconic opened a pull request:

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

    ARTEMIS-1514 Large message fix

    I'm doing an overal improvement on large message support for AMQP
    However this commit is just about a Bug on the converter.
    
    It will be moot after all the changes I'm making, but I would rather keep 
this separate
    as a way to cherry-pick on previous versions eventually.

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

    $ git pull https://github.com/clebertsuconic/activemq-artemis 
amqp-large-message

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

    https://github.com/apache/activemq-artemis/pull/1655.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 #1655
    
----
commit 5e1ae7aa029d4ea53335a893d25bcbe39f4ca423
Author: Clebert Suconic <[email protected]>
Date:   2017-11-13T21:36:47Z

    ARTEMIS-1514 Large message fix
    
    I'm doing an overal improvement on large message support for AMQP
    However this commit is just about a Bug on the converter.
    
    It will be moot after all the changes I'm making, but I would rather keep 
this separate
    as a way to cherry-pick on previous versions eventually.

----


> Implementing AMQP LargeMessage
> ------------------------------
>
>                 Key: ARTEMIS-1514
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1514
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: clebert suconic
>            Assignee: clebert suconic
>             Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to