[
https://issues.apache.org/jira/browse/ARTEMIS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597869#comment-17597869
]
ASF subversion and git services commented on ARTEMIS-3943:
----------------------------------------------------------
Commit d06459df574a66c3cdd29b3ea2addf95792a8566 in activemq-artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=d06459df57 ]
ARTEMIS-3943 Adjusting defalut address settings to avoid OME from paging and
flow control
> Changing Address Settings defaults like Paging Flow Control to avoid OME on
> default configuration on broker
> -----------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3943
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3943
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.24.0
> Reporter: Anton Roskvist
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.25.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> 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:
> {code:java}
> $ 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{code}
> 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:
> {code:java}
> $ broker/bin/artemis consumer \
> --destination TEST \
> --message-count 1 \
> --url "(tcp://localhost:61616)?consumerWindowSize=-1" \
> --sleep 60000{code}
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
