You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2014/03/21 13:24:57 UTC
[jira] [Resolved] (AMQ-5114) AbortSlowAckConsumerStrategy with
abortConnection=false; ensure consumers are always removed from the broker
[ https://issues.apache.org/jira/browse/AMQ-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-5114.
-----------------------------
Resolution: Fixed
fix and test in http://git-wip-us.apache.org/repos/asf/activemq/commit/9bf9e1c0
> AbortSlowAckConsumerStrategy with abortConnection=false; ensure consumers are always removed from the broker
> -------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-5114
> URL: https://issues.apache.org/jira/browse/AMQ-5114
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.9.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.10.0
>
>
> If a consumer is slow and a candidate to abort, the broker sends a control command to the consumer. However there is no guarantee that the consumer will respond to the command and close. As a result the consumer can remain longer than necessary and possibly indefinitely.,
> The broker needs to follow up with a local removeInfo that will force the removal from the broker so that inflight messages can get eagerly redispatched.
> The client can eventually shut down the client view of the consumer but the broker will be able to continue regardless.
--
This message was sent by Atlassian JIRA
(v6.2#6252)