[jira] (ARTEMIS-3928) Paging will flood memory with Native Buffers if too many destinations are used at once

["Robbie Gemmell (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3928 ]


    Robbie Gemmell deleted comment on ARTEMIS-3928:
    -----------------------------------------

was (Author: jira-bot):
Commit ae0d654aae9211d5ff0504aed6b3c465dc7d80a7 in activemq-artemis's branch refs/heads/2.21.0.jbossorg-x from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ae0d654aae ]

ARTEMIS-3928 Adding SoakTest for Paging with in many destinations

Also some organization on soak test to allow this test
adding CLI operation to configure memory size of the broker

(cherry picked from commit 12b81e7a256b1982fafc7e1090134ea1b44d451b)
(cherry picked from commit bbe958985667dd02effc0a735f8d1f09a146ad31)

downstream: ENTMQBR-6797, ENTMQBR-6995


> Paging will flood memory with Native Buffers if too many destinations are used at once
> --------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-3928
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3928
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.24.0
>            Reporter: Clebert Suconic
>            Priority: Major
>             Fix For: 2.25.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> There should be an IO limiter on the number of concurrent readings for Paging.
> Also if openwire is in use, there's no flow control what will also flood the queues with too much data and the broker will also OME.



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