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

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

                Author: ASF GitHub Bot
            Created on: 08/Apr/26 22:36
            Start Date: 08/Apr/26 22:36
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on code in PR #6323:
URL: https://github.com/apache/artemis/pull/6323#discussion_r3054544633


##########
artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/broker/AMQPMessage.java:
##########
@@ -155,7 +155,7 @@ public abstract class AMQPMessage extends RefCountMessage 
implements org.apache.
     * developing purposes.
     */
    public enum MessageDataScanningStatus {
-      NOT_SCANNED(0), SCANNED(1);
+      NOT_SCANNED(0), RELOAD_PERSISTENCE(1), SCANNED(2);

Review Comment:
   I could add anything to not needed parsing... but I'm confused on what 
should I write.
   
   You will stil need the code in place here for version compatbility I 
guess... (or I guess we could just do a full scan if from an older version.
   





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

    Worklog Id:     (was: 1014125)
    Time Spent: 8.5h  (was: 8h 20m)

> Make AMQP Size immutable
> ------------------------
>
>                 Key: ARTEMIS-5573
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5573
>             Project: Artemis
>          Issue Type: Improvement
>          Components: AMQP
>    Affects Versions: 2.41.0
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 8.5h
>  Remaining Estimate: 0h
>
> I have had a lot of issues, even recently on races between re-evaluating a 
> message size in AMQP.
> Say a lazy decode happens at the wrong time and the memory estimates can be 
> wrong.
> We have fixed issues along the years, but this is still a fragile process 
> that is bound to fail. If an user for instance add a plugin breaking the 
> chain of events.
> For that reason the memory estimate should already include enough estimation 
> for any properties decoded and the process should be simplified.
> Less moving parts would mean less possibilities for bugs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to