activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ARTEMIS-1529) AMQP Durable subscriber raised javax.jms.JMSException Maximum Consumer Limit Reached on Queue
Date Wed, 29 Nov 2017 02:05:00 GMT
clebert suconic created ARTEMIS-1529:
----------------------------------------

             Summary: 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)

Mime
View raw message