You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/01/04 20:22:01 UTC
[jira] [Resolved] (ARTEMIS-1529) AMQP Durable subscriber raised
javax.jms.JMSException Maximum Consumer Limit Reached on Queue
[ https://issues.apache.org/jira/browse/ARTEMIS-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-1529.
-------------------------------------
Resolution: Fixed
> AMQP Durable subscriber raised javax.jms.JMSException Maximum Consumer Limit Reached on Queue
> ---------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1529
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1529
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: clebert suconic
> Assignee: clebert suconic
> Fix For: 2.5.0
>
>
> I have regressed this while fixing ARTEMIS-1490:
> https://github.com/apache/activemq-artemis/commit/9eb780cbd16df6b64f97a21a052a1faefd5b4f2b
> The issue is that due to flush connection activity in the AMQP protocol manager, the close may happen while acks are still happening.
> For that reason if you close a consumer too fast you may miss the queue delete.
> for that reason you must recheck the counters again through an operation context async operation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)