[ARTEMIS-2193] Artemis fails on OutOfMemoryError with fast producers

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.6.3, 2.7.0
• Fix Version/s: 2.6.4, 2.8.0
• Component/s: Broker, OpenWire
• Labels: performance
• Assignee: Unassigned
• Reporter: Konrad Kaczkowski
• Created: 05/Dec/18 07:42
• Updated: 27/Jun/19 01:58
• Resolved: 27/Jun/19 01:58

Description

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.

Issue Links

• relates to: ARTEMIS-2200 NPE while dropping/failing large messages on paging
• links to: GitHub Pull Request #2457