You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/16 15:59:40 UTC

[jira] [Resolved] (AMQ-3733) Topic subscriber is assumed to be slow consumer when prefetch is set to one.

     [ https://issues.apache.org/jira/browse/AMQ-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-3733.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.6.0
         Assignee: Gary Tully

fix in http://svn.apache.org/viewvc?rev=1301565&view=rev

thanks for the great test case, makes a fix so much easier :-)
                
> Topic subscriber is  assumed to be slow consumer when prefetch is set to one. 
> ------------------------------------------------------------------------------
>
>                 Key: AMQ-3733
>                 URL: https://issues.apache.org/jira/browse/AMQ-3733
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>            Reporter: Pat Fox
>            Assignee: Gary Tully
>             Fix For: 5.6.0
>
>         Attachments: TopicSubscriptionSlowConsumerTest.patch
>
>
> The broker checks for slow subscribers by checking its dispatch queue size against the prefetch size. If the dispatch queue is greater than or equal to the prefetch size the broker treats this subscription is a slow subscriber. 
> However if the subscribers prefetch size is "1" then the subscription will get treated as a slow subscriber even if the messages do not remain long in the subscription. This can result in a lot of warning log statements 
> {code}
> "TopicSubscription: consumer=... has reached its prefetch limit without an ack, it appears to be slow"
> {code}
> and slow consumer advisory messages being generated if "AdvisoryForSlowConsumers" has been turned on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira