[
https://issues.apache.org/jira/browse/ARTEMIS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711556#comment-16711556
]
Konrad Kaczkowski commented on ARTEMIS-2193:
--------------------------------------------
[~nigro....@gmail.com] Hey! I have attached two heap dumps here:
[https://cernbox.cern.ch/index.php/s/2ih4UYXYYeqNqMl] as they are too large to
be attached in the issue. I briefly compared them and I see many transaction
and journal objects increased significantly over the time.
> 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)
