You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "liuming (JIRA)" <ji...@apache.org> on 2012/09/18 04:43:07 UTC
[jira] [Created] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
liuming created AMQ-4062:
----------------------------
Summary: 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
Priority: Minor
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.
--
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
[jira] [Commented] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457585#comment-13457585 ]
Timothy Bish commented on AMQ-4062:
-----------------------------------
It would be useful if you could create and attach a JUnit test case that demonstrates your issue. This will allow for quicker turnaround and ensure that the fix stays into the future.
> 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
> Priority: Minor
>
> 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
[jira] [Updated] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "liuming (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
liuming updated AMQ-4062:
-------------------------
Attachment: ming.zip
test case.unzip and put it the src/test/java
> 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
> 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
[jira] [Commented] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460361#comment-13460361 ]
Timothy Bish commented on AMQ-4062:
-----------------------------------
I modified the test case and ran it against 5.7-SNAPSHOT tests all pass without issue. A cursory review of the code would seem to indicate that everything is working as it should be.
> 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: AMQ4062Test.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
[jira] [Updated] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQ-4062:
------------------------------
Attachment: AMQ4062Test.java
Modified version of the attached test that puts everything into one file.
> 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: AMQ4062Test.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
[jira] [Commented] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497542#comment-13497542 ]
Timothy Bish commented on AMQ-4062:
-----------------------------------
So far I don't see any way to tell if the sub was just deactivated or is coming back from a clean broker start, seems the only way so far is to only reconfigure on setKeepDurableSubsActive(false)
> 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
[jira] [Resolved] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-4062.
-------------------------------
Resolution: Fixed
Updated fix applied the settings only if keepDurableSubsActive is false the policy is only applied if durable subs go inactive otherwise they retain their original configuration.
> 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
[jira] [Updated] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "liuming (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
liuming updated AMQ-4062:
-------------------------
Attachment: AMQ4062TestNew.java
the code
assertEquals(100, info.getPrefetchSize())
in testSecondStart should be
assertEquals(5, info.getPrefetchSize());
because
policy.setDurableTopicPrefetch(PREFETCH_SIZE_5);
> 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: 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
[jira] [Commented] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462824#comment-13462824 ]
Timothy Bish commented on AMQ-4062:
-----------------------------------
I think I see what's going wrong, will start working on a fix.
> 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: 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
[jira] [Commented] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "liuming (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460130#comment-13460130 ]
liuming commented on AMQ-4062:
------------------------------
I've created a testcase.The PolicyEntry configure the DurableTopicSubscription correctly when there's nothing for the topic in the Kaha storage.When KahaDB contains some messages for that topic,Destination and Subscription info will be recovered and ConsumerInfo will be created in addSubscriptionsForDestination method in TopicRegion class.After that the value of prefetchSize of the ConsumerInfo is zero.
> 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
> 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
[jira] [Commented] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Work started] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Work stopped] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on AMQ-4062 stopped 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
[jira] [Reopened] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-4062.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.7.0
Fixed on trunk.
> 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
[jira] [Comment Edited] (AMQ-4062) durableTopicPrefetch attribute
in policyEntry in activemq.xml dont take effect
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497431#comment-13497431 ]
Gary Tully edited comment on AMQ-4062 at 11/14/12 8:59 PM:
-----------------------------------------------------------
the unusual thing about that test is that it sets a setPendingDurableSubscriberPolicy via a policy, which triggers the reset.
The test works if brokerService.setKeepDurableSubsActive(false) is used.
was (Author: gtully):
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
[jira] [Updated] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "liuming (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
liuming updated AMQ-4062:
-------------------------
Description: 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. (was: 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.)
> 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
> Priority: Minor
>
> 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
[jira] [Assigned] (AMQ-4062) durableTopicPrefetch attribute in
policyEntry in activemq.xml dont take effect
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reassigned AMQ-4062:
---------------------------------
Assignee: 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