Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 22 Feb 2012 16:13:48 +0000 (UTC)
From: "Pat Fox (Updated) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <229003246.4699.1329927228847.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1262401461.4103.1329916548657.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (AMQ-3733) Topic subscriber is  assumed to be slow
 consumer when prefetch is set to one.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Pat Fox updated AMQ-3733:
-------------------------

    Attachment:     (was: TopicSubscriptionSlowConsumerTest.patch)
    
> 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
>         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