Return-Path: 
 <users-return-41334-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-users-archive@www.apache.org
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id CE8A8107E4
	for <apmail-activemq-users-archive@www.apache.org>;
 Fri,  6 Mar 2015 20:44:38 +0000 (UTC)
Received: (qmail 61767 invoked by uid 500); 6 Mar 2015 20:44:35 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 61722 invoked by uid 500); 6 Mar 2015 20:44:35 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 61710 invoked by uid 99); 6 Mar 2015 20:44:35 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Mar 2015 20:44:35 +0000
X-ASF-Spam-Status: No, hits=1.7 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of tbain98@gmail.com designates
 209.85.223.176 as permitted sender)
Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com)
 (209.85.223.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Mar 2015 20:44:09 +0000
Received: by iecar1 with SMTP id ar1so88670793iec.11
        for <users@activemq.apache.org>; Fri, 06 Mar 2015 12:43:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:content-type;
        bh=48X5bETAixfP3p6QiqIXfPUJzvRTpPlfyeWnhKbZkqI=;
        b=sqMQWWHehnPtRQm2YNAqHZEWl+FEXxrqqiWeS2TEQXIS06iBt9QnSLsgskvalkDecx
         aoSJq1nxUi5wLNmv9bVqI2UNM4dVrVyzovd1/JytyV4yZCMiK53hxLslweCTj1MoP7MU
         sL8UAO9x/tcEoqEb8mGp9oPqMj9Tji83M/uGFIcVku/tBewvRLggchfvp2jeqeroLuDx
         oI7PHL079xhoEPaD2LCDePCJNo4/nIVt4qj2VGt460DqH5ePBwB+wFPcIlu+zkQURdfH
         JO2YLQnlxXRL5NA4/1GEmgj1ycoRddGz8IAKEN9g0eOn/KW/J1HscJQbm4E1Nm+qclTv
         9iHQ==
MIME-Version: 1.0
X-Received: by 10.50.72.108 with SMTP id c12mr19043981igv.27.1425674603095;
 Fri, 06 Mar 2015 12:43:23 -0800 (PST)
Sender: tbain98@gmail.com
Received: by 10.50.235.34 with HTTP; Fri, 6 Mar 2015 12:43:22 -0800 (PST)
Received: by 10.50.235.34 with HTTP; Fri, 6 Mar 2015 12:43:22 -0800 (PST)
In-Reply-To: 
 <0EF62BA3BD36B84C9BCC4E12216A74CA1711D1E22A@oxn-mx01.PD.CalAmpCorp.com>
References: 
 <0EF62BA3BD36B84C9BCC4E12216A74CA1711D1E22A@oxn-mx01.PD.CalAmpCorp.com>
Date: Fri, 6 Mar 2015 13:43:22 -0700
X-Google-Sender-Auth: Lb7qvCCGWNVQ9fzhGdjqi3WPXu0
Message-ID: 
 <CAPVVMa_itxtUHGtohQc0wo2jQpPqFxNhAe8tghNknGfR1262Jg@mail.gmail.com>
Subject: Re: PolicyEntry parse order and constantPendingMessageLimitStrategy
 and message counts
From: Tim Bain <tbain@alumni.duke.edu>
To: ActiveMQ Users <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=047d7bdc123c486d300510a4bc2c
X-Virus-Checked: Checked by ClamAV on apache.org

--047d7bdc123c486d300510a4bc2c
Content-Type: text/plain; charset=UTF-8

If the stat is right, you'd see the # bytes used in the store climbing as
well.  (That stat is available in JMX, but I'm not sure it's on the web
console.)
On Mar 6, 2015 11:52 AM, "Matthew Patton" <MPatton@calamp.com> wrote:

> For all the documentation out there I can't find any mention as to parse
> order of activeMQ.xml as it relates to policy entries.
>
> Is it first match? Last match? Most specific match? For example:
>
>                 <policyEntry memoryLimit="64mb" queue="PumpQueue"
> producerFlowControl="false">
>                   <pendingMessageLimitStrategy>
>                     <constantPendingMessageLimitStrategy limit="175000"/>
>                   </pendingMessageLimitStrategy>
>                 </policyEntry>
> ...
>                 <policyEntry memoryLimit="16mb" producerFlowControl="true"
> queue="&gt;">
>                 </policyEntry>
>
> Are my PumpQueue settings being overridden by the wildcard entry that
> comes later?
>
> Also if the limit is 175000 why does Pending Messages (admin/queues.jsp)
> keep climbing way past that number? Are the messages really being discarded
> as intended but it's just that there isn't a metric for discard? How does
> one verify correct behavior?
>
>

--047d7bdc123c486d300510a4bc2c--