[
https://issues.apache.org/jira/browse/ARTEMIS-4798?focusedWorklogId=922228&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922228
]
ASF GitHub Bot logged work on ARTEMIS-4798:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jun/24 16:49
Start Date: 05/Jun/24 16:49
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request, #4961:
URL: https://github.com/apache/activemq-artemis/pull/4961
(no comment)
Issue Time Tracking
-------------------
Worklog Id: (was: 922228)
Remaining Estimate: 0h
Time Spent: 10m
> Address Size differs between Mirror and Source queue, leading to OME scenarios
> ------------------------------------------------------------------------------
>
> Key: ARTEMIS-4798
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4798
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.34.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.35.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Say you configure the broker to mirror.
> You stop the mirror target (shutdown the server).
> Now you send and consume from a destination, keeping the destination's size
> close to zero.
> You may get an OME on that situation.
> This is because the calculation on the address-size only computes the main
> body of the message at the original queue. While Mirror will only get a small
> portion on the reference, in such cases you would end up with lazy starts in
> paging... and things could go wrong.
> To fix that, both Mirror and the source queue should get the body portion of
> the size.
> Basically while we route the message, we check if the address is not the
> original and the Mirror SNF should also get the same portion of the size in
> its calculation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
