[
https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-4062:
-----------------------------
This change seems to break
org.apache.activemq.store.MessagePriorityTest#testDurableSubs
the problem is that the pendingmessage cursor is reset on activate but with the
default keepDurableSubsActive, the state in that cursor about subscribed
destinations is lost.
I think we should not call policyentry.configure if keepDurableSubsActive is
set and we have been deactivated. Not sure if there is an easy way to determine
that.
> 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
