Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/2401
I don't really like the idea of the double threshold. I think the
global-max-size limit should be the catch all case.
What would work better here is an accumulative-max-size setting that
applies to an address space that limits the total amount of memory used by all
addresses that match that address setting. Right now the limits are on a per
address basis, but many addresses can match the same address space.
Doing it this way allows a lot more flexibility in the broker, users can
limit certain address spaces for other reasons that to enable management
messages to flow, like for example, reserving capacity for critical
applications and blocking others. e.g. telemetry.# vs command.#
---
