activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6109) Destination with wildcard may not have correct policy applied
Date Mon, 28 Dec 2015 16:42:49 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072895#comment-15072895
] 

Christopher L. Shannon commented on AMQ-6109:
---------------------------------------------

Patch applied, I will resolve and backport the fixes to 5.12.2 and 5.13.0 if all of the tests
pass.

> 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
>
> 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)

Mime
View raw message