[ARTEMIS-3943] Changing Address Settings defaults like Paging Flow Control to avoid OME on default configuration on broker

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.24.0
• Fix Version/s: 2.25.0
• Assignee: Clebert Suconic
• Reporter: Anton Roskvist
• Created: 17/Aug/22 18:40
• Updated: 30/Aug/22 17:45
• Resolved: 30/Aug/22 13:58

Description

Starting with version 2.24.0 of the broker, a single client can cause the broker to OOM and terminate if an address is paging and holds enough messages to collectively fill the broker heap.

To reproduce:

$ apache-artemis-2.24.0/bin/artemis create broker
$ broker/bin/artemis-service start
$ broker/bin/artemis producer \
  --destination TEST \
  --text-size 100000 \
  --message-count 100000

Optional:
Tweak "message-count" + "text-size" above together with the "-Xmx"-property in artemis.profile to be able to trigger it faster

Kill broker with:

$ broker/bin/artemis consumer \
   --destination TEST \
   --message-count 1 \
   --url "(tcp://localhost:61616)?consumerWindowSize=-1" \
   --sleep 60000

Not saying this is demonstrating proper usage of the client, but this was the easiest way I could think of to reproduce the problem.
Running the same procedure against an older version of the broker results in no such issue

Issue Links

• is duplicated by: ARTEMIS-3928 Paging will flood memory with Native Buffers if too many destinations are used at once
• links to: GitHub Pull Request #4185