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-3233) warnOnProducerFlowControl is never reset to 'true' after the first INFO message is logged.
Date Sat, 02 Nov 2013 20:55:18 GMT

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

Claus Ibsen updated AMQ-3233:
-----------------------------

    Fix Version/s: NEEDS_REVIEWED

> warnOnProducerFlowControl is never reset to 'true' after the first INFO message is logged.
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3233
>                 URL: https://issues.apache.org/jira/browse/AMQ-3233
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2
>         Environment: All
>            Reporter: Adrian Trenaman
>             Fix For: NEEDS_REVIEWED
>
>
> Looking at the code in Queue.java (around line 543), you can see that the warnOnProducerFlowControl
variable is set to false when we log the INFO message "Usage Manager Memory Limit (...) reached
on ....". However, it is never set to true again. So, if we consider operations users trawling
through large logs over a period of time, the may see the first warning on Monday, but then
see no further warnings of this behavior for the rest of the week. Surely we should be resetting
the warnOnProducerFlowControl variable to true, so that subsequent flow control situations
are correctly logged?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message