You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Konrad Kaczkowski (JIRA)" <ji...@apache.org> on 2018/12/05 07:44:00 UTC
[jira] [Updated] (ARTEMIS-2193) Artemis fails on OutOfMemoryError
with fast producers
[ https://issues.apache.org/jira/browse/ARTEMIS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Kaczkowski updated ARTEMIS-2193:
---------------------------------------
Description:
The broker fails on OOM Error in a couple of hours of testing with fast producers:
* The 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
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.
was:
The broker fails on OOM Error in a couple of hours of testing with fast producers:
- The 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
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.
> 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
> Affects Versions: 2.7.0, 2.6.3
> Reporter: Konrad Kaczkowski
> Priority: Critical
> Attachments: broker.xml, log
>
>
> The broker fails on OOM Error in a couple of hours of testing with fast producers:
> * The 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
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)