[jira] [Resolved] (ARTEMIS-2193) Artemis fails on OutOfMemoryError with fast producers

["Justin Bertram (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-2193.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.6.4
                   2.8.0

> Artemis fails on OutOfMemoryError with fast producers
> -----------------------------------------------------
>
>                 Key: ARTEMIS-2193
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2193
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker, OpenWire
>    Affects Versions: 2.6.3, 2.7.0
>            Reporter: Konrad Kaczkowski
>            Priority: Critical
>              Labels: performance
>             Fix For: 2.8.0, 2.6.4
>
>         Attachments: artemis.log, broker.xml, jvm-gc.log, resources_usage.png, screenshot-1.png
>
>
> The broker fails on OOM Error in a couple of hours of testing with fast producers:
>  * The Artemis broker with heap size of 2Gb, global-max-size of 400Mb, and 
>  global address-setting to apply DROP policy whenever memory exceeds 150Mb 
>  (max-size-bytes). 
>  - Two fast producers sending 100 KB messages to 2000 topics every 100 ms each 
>  - Client used: ActiveMQ 5.15.2 JMS
>  - Tested on Artemis 2.6.3 and 2.7.0-SNAPSHOT
>  - Testing time: 2 - 10 h until OOME occurs
> The heap size grows continuously until it runs of out memory. I tested DROP/PAGE/FAIL strategies with no difference. Attached are the log and the broker.xml configuration.
>  
> Expectation: Having sharp memory limits the broker should handle with dropping messages on time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)