activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pat Fox (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-3733) Topic subscriber is assumed to be slow consumer when prefetch is set to one.
Date Wed, 22 Feb 2012 13:15:48 GMT
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

        

Mime
View raw message