[jira] (ARTEMIS-6011) Address fullness not being tracked properly for wildcards

["Justin Bertram (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-6011 ]


    Justin Bertram deleted comment on ARTEMIS-6011:
    -----------------------------------------

was (Author: jira-bot):
Commit c66d2a156f01b5bb62df85761e2356e89276d0a2 in artemis's branch refs/heads/dependabot/maven/com.fasterxml.jackson-jackson-bom-2.22.0 from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=artemis.git;h=c66d2a156f ]

Revert "ARTEMIS-6011 Simplification of checkFullPolicy"
Revert "ARTEMIS-6011 Wildcard routing / Address full or dropped is not properly propagated"

This reverts commit ea9441048c44a8b1d89d27374f7309e5a299ab70.
This reverts commit d21c5c50ac3ceda8cc7d36c72b045eee9f2e7011.


> Address fullness not being tracked properly for wildcards
> ---------------------------------------------------------
>
>                 Key: ARTEMIS-6011
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-6011
>             Project: Artemis
>          Issue Type: Bug
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.54.0
>
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> In use-cases involving consumers using wildcards the broker doesn't track the "fullness" of the address properly. This allows a producer to send more than the allowed amount of message data (e.g. configured via {{max-size-bytes}} or {{max-size-messages}}).
> This is most relevant to MQTT use-cases where wildcards are often used.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org