[jira] [Commented] (AMQ-6901) Destination with wildcard may not have correct policy applied if multiple wildcard policies exist
[ https://issues.apache.org/jira/browse/AMQ-6901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367788#comment-16367788 ] Christopher L. Shannon commented on AMQ-6901: - Added [https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=703b7b151017fe117363e5598146e157bad78265] to fix a NPE > Destination with wildcard may not have correct policy applied if multiple > wildcard policies exist > - > > Key: AMQ-6901 > URL: https://issues.apache.org/jira/browse/AMQ-6901 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.3 >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.16.0, 5.15.4 > > > Back in AMQ-6109 I fixed an issue where the wrong policy was being applied to > a destination. when there were wildcards. It turns out that this was only a > partial fix and there is another edge case where if there are multiple wild > card policies (and some are children) , it is possible for the wrong child > card policy to be applied to a destination at a higher parent level which is > incorrect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-6901) Destination with wildcard may not have correct policy applied if multiple wildcard policies exist
[ https://issues.apache.org/jira/browse/AMQ-6901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367483#comment-16367483 ] ASF subversion and git services commented on AMQ-6901: -- Commit 3c2d5a3015db444de6500dcbe08299d50ce74824 in activemq's branch refs/heads/activemq-5.15.x from [~cshannon] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=3c2d5a3 ] AMQ-6901 - Make sure proper policy is used to configure a destination When multiple wildcard policies exist in a hierarchy it was possible for the wrong policy to be selected when configuring a destination (cherry picked from commit 2ce1c1352fb64ecf1d3018e2b0f7cabeba99b589) > Destination with wildcard may not have correct policy applied if multiple > wildcard policies exist > - > > Key: AMQ-6901 > URL: https://issues.apache.org/jira/browse/AMQ-6901 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.3 >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.16.0, 5.15.4 > > > Back in AMQ-6109 I fixed an issue where the wrong policy was being applied to > a destination. when there were wildcards. It turns out that this was only a > partial fix and there is another edge case where if there are multiple wild > card policies (and some are children) , it is possible for the wrong child > card policy to be applied to a destination at a higher parent level which is > incorrect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-6901) Destination with wildcard may not have correct policy applied if multiple wildcard policies exist
[ https://issues.apache.org/jira/browse/AMQ-6901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367482#comment-16367482 ] ASF subversion and git services commented on AMQ-6901: -- Commit 2ce1c1352fb64ecf1d3018e2b0f7cabeba99b589 in activemq's branch refs/heads/master from [~cshannon] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=2ce1c13 ] AMQ-6901 - Make sure proper policy is used to configure a destination When multiple wildcard policies exist in a hierarchy it was possible for the wrong policy to be selected when configuring a destination > Destination with wildcard may not have correct policy applied if multiple > wildcard policies exist > - > > Key: AMQ-6901 > URL: https://issues.apache.org/jira/browse/AMQ-6901 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.3 >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.16.0, 5.15.4 > > > Back in AMQ-6109 I fixed an issue where the wrong policy was being applied to > a destination. when there were wildcards. It turns out that this was only a > partial fix and there is another edge case where if there are multiple wild > card policies (and some are children) , it is possible for the wrong child > card policy to be applied to a destination at a higher parent level which is > incorrect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
