[jira] [Resolved] (AMQ-6109) Destination with wildcard may not have correct policy applied

["Christopher L. Shannon (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher L. Shannon resolved AMQ-6109.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 5.14.0
                   5.13.1
                   5.12.2

> Destination with wildcard may not have correct policy applied
> -------------------------------------------------------------
>
>                 Key: AMQ-6109
>                 URL: https://issues.apache.org/jira/browse/AMQ-6109
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.12.1, 5.13.0
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>             Fix For: 5.12.2, 5.13.1, 5.14.0
>
>
> When a destination is created with a wildcard, it may not have the correct policy applied.  
> For example, if there are two policies:
> {code:xml}
> <policyMap>
>     <policyEntries>
>          <policyEntry queue="test.queue.>" memoryLimit="20mb" />
>          <policyEntry queue="test.queue.a" memoryLimit="5000000"  />
>      </policyEntries>
> </policyMap>
> {code}
> and if the queue {{test.queue.>}} is created, the policy for {{test.queue.a}} will be applied to that destination instead of the {{test.queue.>}} policy.
> Some work was done on this in AMQ-5972 and that seems to have fixed most of the issues, but there is this one edge case where we need to account for what happens if a policy matches a destination exactly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)