You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2008/07/22 19:47:00 UTC
[jira] Commented: (AMQ-1866) Using small queue prefetch sizes cause
all consumers to run as fast as the slowest consumer.
[ https://issues.apache.org/activemq/browse/AMQ-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44438#action_44438 ]
Hiram Chirino commented on AMQ-1866:
------------------------------------
test case AMQ1866.java has been added to trunk. Currently failing it show a test case the works for the default prefetch but which fails for small prefetches.
> Using small queue prefetch sizes cause all consumers to run as fast as the slowest consumer.
> --------------------------------------------------------------------------------------------
>
> Key: AMQ-1866
> URL: https://issues.apache.org/activemq/browse/AMQ-1866
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
>
> If you have a JMS producer sending messages to multiple consumers and you have the cacheLevel set to 3 or higher, eventually all consumers will run as slow as the slowest consumer.
> In the attached projects the SA sends messages to a MockOptimizer (JMS consumer) that has two threads. One sleeps for one second and the other sleeps for ten. Initially the thread sleeping for 1 second will consume most of the messages, but towards the end it will start to consume messages every ten seconds as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.