You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2018/09/03 13:58:00 UTC

[jira] [Updated] (ARTEMIS-2068) broker should avoid reading any file to get AMQP large msg size

     [ https://issues.apache.org/jira/browse/ARTEMIS-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell updated ARTEMIS-2068:
------------------------------------
    Fix Version/s:     (was: 2.6.3)
                   2.7.0
      Description: 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.  (was: AMQP JMS is reading the whole file containing a large message each time the body size length is needed. It should avoid that cost just by reading the file size.)
          Summary: broker should avoid reading any file to get AMQP large msg size  (was: AMQP JMS should avoid reading any file to get large msg size)

Tweaked title and description to remove mention of JMS or any other client (since it isn't due to, or able to be influenced by, the clients), and updated version to 2.7.0 for now since 2.6.3 is currently under vote so this couldn't be changed there without a respin. Seems more like a reason to do a 2.6.4.

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