[
https://issues.apache.org/jira/browse/ARTEMIS-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386421#comment-16386421
]
ASF GitHub Bot commented on ARTEMIS-1730:
-----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/1930
ARTEMIS-1730 fix expiry without address or bindings
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1730
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1930.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 #1930
----
commit 1a317354692dd4f23ec3c703ac169b5b9bafaff6
Author: Justin Bertram <jbertram@...>
Date: 2018-03-05T17:39:58Z
ARTEMIS-1730 fix expiry without address or bindings
----
> Server leaks memory when messages are expired without an expiry-address
> -----------------------------------------------------------------------
>
> Key: ARTEMIS-1730
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1730
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.4.0
> Reporter: Ilkka Virolainen
> Assignee: Justin Bertram
> Priority: Major
>
> When messages are being expired from an address that has an empty
> expiry-address they should be dropped. At the moment what happens is that the
> broker logs a message indicating that the message is being dropped:
> AMQ222146: Message has expired. No bindings for Expiry Address so dropping
> it
> However, the messages are never acknowledged so they end up showing as in
> delivery. ExpiredCount for the queue is never incremented while
> DeliveringCount is. This results in increased memory consumption and as the
> amount of expiring messages increase the broker eventually runs out of memory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
