[
https://issues.apache.org/jira/browse/ARTEMIS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709854#comment-16709854
]
Francesco Nigro commented on ARTEMIS-2193:
------------------------------------------
Hi!!
I can see several things:
# the address settings on management addresses are no longer valid due to
(check https://github.com/apache/activemq-artemis/pull/2414): [Paging
doc|https://github.com/franz1981/activemq-artemis/blob/3b03f1e337b87e006296ff0e6ac1a194cadd39f6/docs/user-manual/en/paging.md]
# {quote}2018-12-05 04:50:55,776 WARN
[org.apache.activemq.artemis.core.server] Errors occurred during the buffering
operation : javax.jms.IllegalStateException: not implemented!{quote}
It is happening before the OOM error too? How many times?
# 100 KB messages to 2000 topics: not sure, but OpenWire don't allow large
messages chucked encoding/decoding/streaming
It would be great if you can provide some heap snapshots with JMC or JVisualVM
to find if there is any evident memory leak: it would help to speedup any
investigation (y)
Considering the DROP policy it looks to me like a bug (that's just a guess).
> 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: broker.xml, log
>
>
> 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)
