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 2017/11/29 02:21:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16269947#comment-16269947 ]
ASF GitHub Bot commented on ARTEMIS-1529:
-----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/1678
ARTEMIS-1529 Fixing Ref count over asynchronous ack
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis ARTEMIS-1529
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1678.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 #1678
----
commit f989a7ae959b9a61ac3dcfedcae0541ba402508f
Author: Tomas Kratky <tk...@redhat.com>
Date: 2017-11-28T21:37:46Z
ARTEMIS-1529 Adding test on durable topics
commit ee6a0fe6fadf670e4691b2e19e21aaef8b79d92d
Author: Clebert Suconic <cl...@apache.org>
Date: 2017-11-29T02:08:05Z
ARTEMIS-1529 Fixing Ref count over asynchronous ack
----
> 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 Proton, 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)