You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/03/05 17:44:00 UTC
[jira] [Updated] (ARTEMIS-1730) Server leaks memory when messages
are expired without an expiry-address
[ https://issues.apache.org/jira/browse/ARTEMIS-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated ARTEMIS-1730:
------------------------------------
External issue URL: http://mail-archives.apache.org/mod_mbox/activemq-users/201802.mbox/%3cf9edeca99c924bfe90faddbc5bde5e2c@exchange.intra.bitwise.fi%3e
> 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, 2.5.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)