Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 14 Nov 2012 20:58:12 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <285163303.115685.1352926692335.JavaMail.jiratomcat@arcas>
In-Reply-To: <1396294622.90837.1347936187677.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (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


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

Gary Tully commented on AMQ-4062:
---------------------------------

the unusual thing about that test is that it sets a setPendingDurableSubscriberPolicy via a policy, which triggers the reset.
                
> 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
>             Fix For: 5.7.0
>
>         Attachments: AMQ4062Test.java, AMQ4062TestNew.java, 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