You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2006/11/13 22:43:10 UTC

[jira] Updated: (AMQ-132) Remotting logging of clients under flow control

     [ https://issues.apache.org/activemq/browse/AMQ-132?page=all ]

Hiram Chirino updated AMQ-132:
------------------------------

    Fix Version/s: 4.2
                       (was: 4.1.0)

> Remotting logging of clients under flow control
> -----------------------------------------------
>
>                 Key: AMQ-132
>                 URL: https://issues.apache.org/activemq/browse/AMQ-132
>             Project: ActiveMQ
>          Issue Type: New Feature
>            Reporter: Barry Kaplan
>             Fix For: 4.2.0
>
>
> When performance testing a system (or troubleshooting slowdowns in production) it would be very helpful to know when any client has come under flow control. This information would be logged (via jmx events?) including the identification of the broker(s) that cannot keep up, and the corresponding client(s) that have been throttled.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira