[
https://issues.apache.org/jira/browse/AMQ-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Earls closed AMQ-5019.
----------------------------
Resolution: Not A Problem
This was fixed on the trunk as part of AMQ-4930. The current code looks like:
LOG.info("{}, Usage Manager memory limit reached {}. 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.",
getActiveMQDestination().getQualifiedName(),
memoryUsage.getLimit());
> Typos bug in Topic.java class
> ------------------------------
>
> Key: AMQ-5019
> URL: https://issues.apache.org/jira/browse/AMQ-5019
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.9.0
> Reporter: Yuriy Sidelnikov
> Priority: Minor
>
> The LOG.info has two {} elements but only one reference:
> LOG.info("{}, Usage Manager memory limit reached for {}.
> 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.",
> getActiveMQDestination().getQualifiedName());
> As a result it is providing a confusing message such as:
> 2014-01-15 10:29:20,073 INFO - topic://consumer_out, Usage Manager memory
> limit reached for {}. 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.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
