You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2018/10/16 14:16:00 UTC

[jira] [Created] (AMQ-7077) Queue subscriber view slowConsumer flag set in error

Gary Tully created AMQ-7077:
-------------------------------

             Summary: Queue subscriber view slowConsumer flag set in error
                 Key: AMQ-7077
                 URL: https://issues.apache.org/jira/browse/AMQ-7077
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.15.0
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.16.0


For queue subscribers, the broker dispatches prefetch num messages and stops. The subscription is considered full.

There is currently logic in PrefetchSubscription that flags the consumer as slow on the success full dispatch of the last message in a prefetch batch. this flag remains set till there are more messages to dispatch, which happens on the first ack.

The consumer is considered slow, till it acks (which seems wrong) and in the case that there are no more message to dispatch, it remains slow.

 

Interestingly, there are some tests for this functionality that only validate topics in error.

 

From my investigation, it seems that for queue consumers, it is really only possible to gauge slowness due to the frequency of acks, which is what the AbortAckSlowConsumerPolicy does.

It makes sense that that code flags a consumer as slow once it is detected as such.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)