activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gaohoward <...@git.apache.org>
Subject [GitHub] activemq-artemis pull request #1532: ARTEMIS-1419 OpenWire advisory message ...
Date Wed, 13 Sep 2017 12:57:50 GMT
GitHub user gaohoward opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1532

    ARTEMIS-1419 OpenWire advisory message never deleted

    By default, every openwire connection will create a queue
    under the multicast address ActiveMQ.Advisory.TempQueue.
    If a openwire client is create temporary queues these queues
    will fill up with messages for as long as the associated
    openwire connection is alive. It appears these messages
    do not get consumed from the queues.
    
    The reason behind is that advisory messages don't require
    acknowledgement so the messages stay at the queue.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gaohoward/activemq-artemis kmaster_1419

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1532.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 #1532
    
----
commit 853571229851ee2592aedf61e005b530987943fd
Author: Howard Gao <howard.gao@gmail.com>
Date:   2017-09-13T12:50:56Z

    ARTEMIS-1419 OpenWire advisory message never deleted
    
    By default, every openwire connection will create a queue
    under the multicast address ActiveMQ.Advisory.TempQueue.
    If a openwire client is create temporary queues these queues
    will fill up with messages for as long as the associated
    openwire connection is alive. It appears these messages
    do not get consumed from the queues.
    
    The reason behind is that advisory messages don't require
    acknowledgement so the messages stay at the queue.

----


---

Mime
View raw message