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 GitHub Bot (Jira)" <ji...@apache.org> on 2022/08/09 21:16:00 UTC

[jira] [Work logged] (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?focusedWorklogId=799511&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-799511 ]

ASF GitHub Bot logged work on ARTEMIS-3928:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Aug/22 21:15
            Start Date: 09/Aug/22 21:15
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic opened a new pull request, #4173:
URL: https://github.com/apache/activemq-artemis/pull/4173

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




Issue Time Tracking
-------------------

            Worklog Id:     (was: 799511)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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: 10m
>  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)