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 subversion and git services (Jira)" <ji...@apache.org> on 2022/08/10 20:40:00 UTC
[jira] [Commented] (ARTEMIS-3928) Paging will flood memory with Native Buffers if too many destinations are used at once
[ https://issues.apache.org/jira/browse/ARTEMIS-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578146#comment-17578146 ]
ASF subversion and git services commented on ARTEMIS-3928:
----------------------------------------------------------
Commit 12b81e7a256b1982fafc7e1090134ea1b44d451b in activemq-artemis's branch refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=12b81e7a25 ]
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
> 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: 20m
> 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)