[ https://issues.apache.org/jira/browse/ARTEMIS-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578183#comment-17578183 ]
ASF subversion and git services commented on ARTEMIS-3928: ---------------------------------------------------------- Commit 568eb70fcda9737b38871a3bff1e111bad784091 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=568eb70fcd ] ARTEMIS-3929 Improving OpenWire clientIDSet I have seen this contention while I was testing ARTEMIS-3928 This does change any semantics and current tests should be enough to validate this change > 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)