Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B60B2DC6A for ; Fri, 21 Sep 2012 08:47:15 +0000 (UTC) Received: (qmail 67197 invoked by uid 500); 21 Sep 2012 08:47:14 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 66768 invoked by uid 500); 21 Sep 2012 08:47:12 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 66248 invoked by uid 99); 21 Sep 2012 08:47:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2012 08:47:09 +0000 Date: Fri, 21 Sep 2012 19:47:09 +1100 (NCT) From: "Timothy Bish (JIRA)" To: dev@activemq.apache.org Message-ID: <1039325806.106975.1348217229813.JavaMail.jiratomcat@arcas> In-Reply-To: <1396294622.90837.1347936187677.JavaMail.jiratomcat@arcas> Subject: [jira] [Work started] (AMQ-4062) durableTopicPrefetch attribute in policyEntry in activemq.xml dont take effect 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-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-4062 started by Timothy Bish. > durableTopicPrefetch attribute in policyEntry in activemq.xml dont take effect > ------------------------------------------------------------------------------ > > Key: AMQ-4062 > URL: https://issues.apache.org/jira/browse/AMQ-4062 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.6.0 > Environment: windows XP jdk1.6 > Reporter: liuming > Assignee: Timothy Bish > Priority: Minor > Attachments: ming.zip > > > There are three methods to configure the prefetchSize of a consumer,per broker,per connection and per destination.I configured the policyEntry element in activemq.xml and set durableTopicPrefetch="5".Then a durable topic Consumer connected to the broker ,but the prefetchSize instance variable of ConsumerInfo object was 100, the default value for durable topic consumer.Some messages of the topic consumer were stored in the kahaDB. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira