Currently, we have a single-tier address-full-policy that triggers whenever either max-size-bytes or max-size-messages is hit for the address. This enhancement would allow configuration of two tiers of behavior. For example we could have a max-size-bytes threshold for paging and a paging quota that would result in BLOCK or FAIL behavior when the page space quota is exhausted.

Use case:

If we implement an address-setting like this with a policy of BLOCK or FAIL, all the messages are kept in memory which increases memory overhead, increasing potential to exhaust heap space. On the other hand, if we configure an address of a policy of PAGE, it could continue to accept messages until the volume usage limit is reached, which then results in a potentially catastrophic blocking behavior for all addresses.

This would allow paging quotas to be configured at the address level to avoid the all or nothing behavior above.