You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2009/09/28 15:23:51 UTC

[jira] Created: (AMQ-2428) Improve producer flow control logging

Improve producer flow control logging
-------------------------------------

                 Key: AMQ-2428
                 URL: https://issues.apache.org/activemq/browse/AMQ-2428
             Project: ActiveMQ
          Issue Type: Improvement
          Components: Broker
    Affects Versions: 5.3.0
            Reporter: Dejan Bosanac
            Assignee: Dejan Bosanac


Currently we log a info message immediately after producer is stopped on some system usage limit. We do so just for the first time for memory limits, to prevent flooding the log. It would be good to log message only if producer is stopped for specified (configurable) amount of time, and thus avoid flooding the log in these edge cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AMQ-2428) Improve producer flow control logging

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-2428:
------------------------------

    Fix Version/s: 5.5.0
                       (was: 5.4.1)

> Improve producer flow control logging
> -------------------------------------
>
>                 Key: AMQ-2428
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2428
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.3.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.5.0
>
>
> Currently we log a info message immediately after producer is stopped on some system usage limit. We do so just for the first time for memory limits, to prevent flooding the log. It would be good to log message only if producer is stopped for specified (configurable) amount of time, and thus avoid flooding the log in these edge cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.