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

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

GitHub user franz1981 opened a pull request:

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

    ARTEMIS-2068 save reading any file to get AMQP large msg size

    ServerJMSBytesMessage::getBodyLength can save reading
    the whole large message file by reading just its
    file size

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

    $ git pull https://github.com/franz1981/activemq-artemis ARTEMIS-2068

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

    https://github.com/apache/activemq-artemis/pull/2294.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 #2294
    
----
commit 03046508b11dbaee7b04648578744f4db74236da
Author: Francesco Nigro <nigro.fra@...>
Date:   2018-09-03T06:57:11Z

    ARTEMIS-2068 save reading any file to get AMQP large msg size
    
    ServerJMSBytesMessage::getBodyLength can save reading
    the whole large message file by reading just its
    file size

----


> broker should avoid reading any file to get AMQP large msg size
> ---------------------------------------------------------------
>
>                 Key: ARTEMIS-2068
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2068
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: AMQP, Broker
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Major
>             Fix For: 2.7.0
>
>
> The broker is reading the whole file containing a large AMQP message each 
> time the body size length is needed. It should avoid that cost just by 
> reading the file size.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to