activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-3234) Memory usage limits may be reported incorrectly.
Date Sat, 02 Nov 2013 20:55:18 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated AMQ-3234:
-----------------------------

    Fix Version/s: NEEDS_REVIEWED

> 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
>             Fix For: NEEDS_REVIEWED
>
>
> 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
(v6.1#6144)

Mime
View raw message