You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2016/10/21 18:42:59 UTC
[jira] [Closed] (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:all-tabpanel ]
clebert suconic closed ARTEMIS-767.
-----------------------------------
> 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)