[
https://issues.apache.org/jira/browse/ARTEMIS-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165384#comment-16165384
]
ASF subversion and git services commented on ARTEMIS-1419:
----------------------------------------------------------
Commit e4fb722ad8480dd12c037230706ef97d9a57f801 in activemq-artemis's branch
refs/heads/master from [~gaohoward]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=e4fb722 ]
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.
> OpenWire advisory message never deleted
> ---------------------------------------
>
> Key: ARTEMIS-1419
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1419
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 2.3.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Fix For: 2.4.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
