[
https://issues.apache.org/jira/browse/ARTEMIS-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699063#comment-17699063
]
ASF subversion and git services commented on ARTEMIS-4162:
----------------------------------------------------------
Commit 294daa0ff6a608813694818812d2a4a1a7702146 in activemq-artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=294daa0ff6 ]
ARTEMIS-4162 Remove EMPTY_ROUTING_TYPES from AddressInfo
I have seen a werid intermittent failure in the testsuite
caused by some race where the EMPTY_SET ends up Not Empty! Causing weird
failures that were really difficult to be investigated
> Support deleting addresses and queues without usage check
> ---------------------------------------------------------
>
> Key: ARTEMIS-4162
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4162
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> There are certain use-cases where addresses will be auto-created and never
> have a direct binding created on them. Because of this they will never be
> auto-deleted. If a large number of these addresses build up they will consume
> a problematic amount of heap space.
> One specific example of this use-case is an MQTT subscriber with a wild-card
> subscription and a large number of MQTT producers sending one or two messages
> a large number of different MQTT topics covered by the wild-card. Since
> consumers are never created on any of these individual addresses they will
> never be auto-deleted, but they will eventually consume a large amount of
> heap. The only way to deal with these addresses is to manually delete them.
> We should have a way to tell the address reaper to skip the usage check.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
