[
https://issues.apache.org/jira/browse/AMQ-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266270#comment-17266270
]
Matt Pavlovich commented on AMQ-3234:
-------------------------------------
[~adrian.trenaman] This issue is quite dated and most likely resolved up
through in 5.16.1. Please update with a reproducible test case against 5.16.1
if this is still an issue for you.
NOTE: This JIRA is scheduled to close in 30 days if no update is provided.
> Memory usage limits may be reported incorrectly.
> --------------------------------------------------
>
> Key: AMQ-3234
> URL: https://issues.apache.org/jira/browse/AMQ-3234
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Environment: All
> Reporter: Adrian Trenaman
> Priority: Major
> Fix For: NEEDS_REVIEW
>
>
> The determination of whether memory usage 'isFull' is performed by first
> checking if the parent memory usage is full, and the checking if the queue's
> memory usage itself is full (See line 91 of MemoryUsage.java). However, the
> reporting of a memory usage full event (at line 548 of Queue.java, reproduced
> below) creates a message based on the memory usage of the queue alone. So,
> it's possible that a memory limit may be hit because of the overall Broker
> memory being consumed, but it will be reported as a limit breach of a smaller
> queue memory usage amount.
> {code}
> LOG.info("Usage Manager Memory Limit ("
> + memoryUsage.getLimit()
> + ") reached on "
> + getActiveMQDestination().getQualifiedName()
> + ". Producers will be throttled to the rate at which messages are removed
> from this destination to prevent flooding it."
> + " See http://activemq.apache.org/producer-flow-control.html for more
> info");
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
