You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/20 13:31:00 UTC

[jira] [Work logged] (ARTEMIS-2669) Improve AMQPStandardMessage::reencode on depaging not durable messages

     [ https://issues.apache.org/jira/browse/ARTEMIS-2669?focusedWorklogId=407039&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-407039 ]

ASF GitHub Bot logged work on ARTEMIS-2669:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Mar/20 13:30
            Start Date: 20/Mar/20 13:30
    Worklog Time Spent: 10m 
      Work Description: franz1981 commented on pull request #3036: ARTEMIS-2669 Improve AMQPStandardMessage::reencode on depaging not durable messages
URL: https://github.com/apache/activemq-artemis/pull/3036
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 407039)
    Remaining Estimate: 0h
            Time Spent: 10m

> Improve AMQPStandardMessage::reencode on depaging not durable messages
> ----------------------------------------------------------------------
>
>                 Key: ARTEMIS-2669
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2669
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP, Broker
>    Affects Versions: 2.11.0
>            Reporter: Francesco Nigro
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently depaging AMQP not durable messages turn them into durable ones (with the Header section created) and reencoded again: the reencode could be optimized by preserving  and limiting the amount of buffer copies and Java object allocations in specific cases.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)