[
https://issues.apache.org/activemq/browse/AMQ-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-132.
----------------------------
Fix Version/s: 5.1.0
(was: 5.2.0)
Resolution: Fixed
This is noe straightforward to do by monitoring memory limits and pending
message count for a subscriber in JMX
> 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
> Assignee: Rob Davies
> Fix For: 5.1.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.
-
You can reply to this email to add a comment to the issue online.
