You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Fraser Adams (Updated) (JIRA)" <ji...@apache.org> on 2012/04/20 20:06:41 UTC

[jira] [Updated] (QPID-3869) Connection Logger tool (QMF1/python) connection-logger is used to provide detailed information about connections made to a broker.

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

Fraser Adams updated QPID-3869:
-------------------------------

    Attachment: connection-logger

Updated with more or less a complete rewrite of the algorith.

The original version is functionally fine but it uses linear searches to dereference QMF Object References (pretty similar to qpid-config really). This is OK and quite readable, but for large numbers of Connections/Queues the performance gets totally trashed.

The latest version dereferences the QMF objects into Maps keyed by ObjectId it also resolves the 0..* associations between Connection and Session and Session and Subscription in order to work out which connections are likely to be producer only Connections.
                
> Connection Logger tool (QMF1/python) connection-logger is used to provide detailed information about connections made to a broker.
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-3869
>                 URL: https://issues.apache.org/jira/browse/QPID-3869
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Python Tools
>         Environment: Python QMF1 tools
>            Reporter: Fraser Adams
>            Priority: Minor
>         Attachments: connection-logger, connection-logger
>
>
> connection-logger is used to provide information about connections made to a broker.
> Using qpid-stat for connections is OK but it doesn't provide information as to whether a connection relates to a producer or consumer as this information can only really be derived from the associations between connection, session and binding.
> The Connection Logger tool creates the associations and displays information based on this additional knowledge.
> In default mode connection-logger lists the connections made to a broker along with information about sessions such as whether any subscriptions are associated with the session (if a session has no subscriptions then it's quite likely to be a "producer only" session, so this knowledge is quite useful).
> In "log queue and binding" mode the information provided is very similar to qpid-config -b queues but with additional connection related information provided as with default mode.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org