You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org> on 2010/08/08 05:13:16 UTC
[jira] Resolved: (QPID-2178) Allow viewing of channel flow control
status via JMX Management Console
[ https://issues.apache.org/jira/browse/QPID-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-2178.
----------------------------------
Resolution: Fixed
Bulk resolution of old JMX Management Console issues
> Allow viewing of channel flow control status via JMX Management Console
> -----------------------------------------------------------------------
>
> Key: QPID-2178
> URL: https://issues.apache.org/jira/browse/QPID-2178
> Project: Qpid
> Issue Type: New Feature
> Components: Java Management : JMX Console, Java Management : JMX Interface
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.6
>
>
> When Flow Control is being utilised on the broker, it may be useful to expose the status of a channel (based on thevalue of _blocking in AMQChannel) as a read-only property via the management console.
> Channel properties are currently only exposed by the broker over JMX via the ManagedConnection mbean interface which defines a channels() method implemented in the AMQProtocolSessionMBean, that returns a data set consisting of channel id, transactional status, default queue, and number of unacked messages for all channels on the connection. In order to expose the flow controlled status of the channel, this result set would be expanded to include the value of the new _blocking AtomicBoolean within AMQSession.
> Expanding the result set would not affect compatability with the older console UI, which should automatically display it thanks to its completely generic construction. The new console UI utilises this particular information set quite differently in order to construct a structured table and would not make use of the additional information until modified to do so (its presence would not interfere until that time, it simply wont be utilised) by performing a small update to add a new table column when the additional information is available on supporting brokers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org