[
https://issues.apache.org/jira/browse/ARTEMIS-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Nigro updated ARTEMIS-3577:
-------------------------------------
Description:
ARTEMIS-3021 has introduced a check re encoding validity while computing memory
estimate.
It means that if a message modified after being copied and encoded, it would be
re-encoded while computing memory estimation: this is happening while moving
messages, because the destination address is added after checking for large
message that's causing a stealth message encoding.
was:
ARTEMIS-3021 has introduced a more precise Core message memory estimation, but
checking the encoded size after copied (to detect if msg should be treated as
large) cause the msg to be encoded: any subsequent change on the msg eg
changing its address, would cause the msg to be re-encoded.
This unnecessary re-encoding could be saved by performing address modification
before checking the encoded size.
> Save Core msg re-encoding due to msg copy
> -----------------------------------------
>
> Key: ARTEMIS-3577
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3577
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Minor
>
> ARTEMIS-3021 has introduced a check re encoding validity while computing
> memory estimate.
> It means that if a message modified after being copied and encoded, it would
> be re-encoded while computing memory estimation: this is happening while
> moving messages, because the destination address is added after checking for
> large message that's causing a stealth message encoding.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
