You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/10/07 17:24:21 UTC

[jira] [Commented] (ARTEMIS-767) False CONSUMER_SLOW notifications using core api consumer with PRE_ACKNOWLEDGE mode

    [ https://issues.apache.org/jira/browse/ARTEMIS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555689#comment-15555689 ] 

ASF GitHub Bot commented on ARTEMIS-767:
----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/825

    ARTEMIS-767 consumer with pre-ack flagged as slow

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-767

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/825.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #825
    
----
commit afb15e41241555e2c770a5ffb6e0dc7ef413b876
Author: jbertram <jb...@apache.com>
Date:   2016-10-07T16:43:19Z

    ARTEMIS-767 consumer with pre-ack flagged as slow

----


> False CONSUMER_SLOW notifications using core api consumer with PRE_ACKNOWLEDGE mode
> -----------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-767
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-767
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.1.0
>         Environment: Redhat Linux 2.6
>            Reporter: Ruben Cala
>            Assignee: Justin Bertram
>             Fix For: 1.5.0
>
>
> When using a core api ClientConsumer using pre-acknowledge message acknowledgement, the broker sends out CONSUMER_SLOW notifications (continuously) for that client.  According to JConsole, the queue for the client shows all messages being acknowledged, and the address for the queue shows address size = 0 (not backing up).  The ClientSession used to create the consumer was constructed with the pre-acknowledge constructor param=true:
> ...
> ClientSession session = factory.createSession(false, true, true, true);
> I also noticed that this does not happen using a STOMP client using the auto acknowledgment subscription (with "ack:auto" header in SUBSCRIBE frame).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)