Return-Path: 
 <issues-return-4807-apmail-activemq-issues-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-issues-archive@minotaur.apache.org
Delivered-To: apmail-activemq-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C21CF184E1
	for <apmail-activemq-issues-archive@minotaur.apache.org>;
 Mon, 28 Dec 2015 16:42:49 +0000 (UTC)
Received: (qmail 52678 invoked by uid 500); 28 Dec 2015 16:42:49 -0000
Delivered-To: apmail-activemq-issues-archive@activemq.apache.org
Received: (qmail 52630 invoked by uid 500); 28 Dec 2015 16:42:49 -0000
Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@activemq.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@activemq.apache.org>
List-Post: <mailto:issues@activemq.apache.org>
List-Id: <issues.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list issues@activemq.apache.org
Received: (qmail 52611 invoked by uid 99); 28 Dec 2015 16:42:49 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Dec 2015 16:42:49 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 8FC972C1F54
	for <issues@activemq.apache.org>; Mon, 28 Dec 2015 16:42:49 +0000 (UTC)
Date: Mon, 28 Dec 2015 16:42:49 +0000 (UTC)
From: "Christopher L. Shannon (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12924527.1451320766000.16343.1451320969586@Atlassian.JIRA>
In-Reply-To: <JIRA.12924527.1451320766000@Atlassian.JIRA>
References: <JIRA.12924527.1451320766000@Atlassian.JIRA>
 <JIRA.12924527.1451320766707@arcas>
Subject: [jira] [Commented] (AMQ-6109) Destination with wildcard may not
 have correct policy applied
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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