Bug 746988 - When Cumin is connected to multiple brokers the 'Connections' tab does not filter connections by broker
Summary: When Cumin is connected to multiple brokers the 'Connections' tab does not fi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: cumin
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: grid-maint-list
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-18 13:49 UTC by Trevor McKay
Modified: 2016-05-26 19:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-26 19:37:07 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Trevor McKay 2011-10-18 13:49:14 UTC
Description of problem:

Connected Cumin to 3 brokers.  Drilled into each broker, went to the Connections tab.  All of the connections for all 3 brokers are displayed under the Connections tab for each of the brokers.  The list should be filtered for the particular broker.

Discovered while investigating customer questions.

Version-Release number of selected component (if applicable):

This code hasn't changed for quite a while, assuming 2.0 (or even 1.3) but I haven't tested that.

How reproducible:

100%

Steps to Reproduce:
1.  Specify multiple brokers in the cumin.conf file.
2.  Drill into each and look at the connections.  Connections can be differentiated by looking at the IP addresses involved, or by running different apps on different hosts (condor, qpid-tool, qpid-stat, etc)
  
Actual results:

All connections in the Cumin database are displayed.

Expected results:

Connections ought to be filtered by broker we've drilled into to get to the Connections tab.

Additional info:

It seems to me that Exchanges, Queues, etc are working correctly but we might want to check those too.

Comment 1 Anne-Louise Tangring 2016-05-26 19:37:07 UTC
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.


Note You need to log in before you can comment on or make changes to this bug.