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

["Francesco Nigro (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711125#comment-16711125 ] 

Francesco Nigro edited comment on ARTEMIS-2193 at 12/6/18 8:46 AM:
-------------------------------------------------------------------

[~kkaczkow]After ~30 minutes the GC was unable to perform minor collections that were cleaning up the young generation and the instances started to get promoted ie there was something on the heap that cannot be deleted.
My suggestion is to take 2 heap snapshots at the distance of ~10 mintues: 1 after 5 minutes that the broker is started and the second 10 after it.
JVisualVM (or JMC) allow to see the diff of those snapshots and it would help to see which instances are just increased and are bloating the heap.


was (Author: nigro.fra@gmail.com):
[~kkaczkow]After ~30 minutes the GC was unable to perform minor collections that were cleaning up the young generation and the instances started to get promoted ie there was something on the heap that cannot be deleted.
My suggestion is to take 2 heap snapshots at the distance of ~10 mintues: 1 after 5 minutes that the broker is started and the second 10 after it.
JVisualVM (or JMC) allow to see the diff of those snapshots and it would help to see which instances are just increased are bloating the heap.

> 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.7.0, 2.6.3
>            Reporter: Konrad Kaczkowski
>            Priority: Critical
>              Labels: performance
>         Attachments: artemis.log, broker.xml, jvm-gc.log, resources_usage.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)