Bug 891673 - qpid-tools to support broker-list and reconnect option
Summary: qpid-tools to support broker-list and reconnect option
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-tools
Version: 2.3
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: Messaging QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-03 15:57 UTC by Pavel Moravec
Modified: 2025-02-10 03:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:27:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Moravec 2013-01-03 15:57:17 UTC
Description of problem:
Since new HA introduced, customers have a cluster of brokers where just (the active) one physically accepts new connections and others reject them. If one does not use virtual IP address in cluster configuration, using qpid tools gets complicated as:
- they don't support reconnect either broker-list in "-b" option
- thus one has to check what broker is the active one and even then fire his/her command

Therefore it makes sense to enhance qpid tools by reconnect option as well as allow broker-list in "-b" option.


Version-Release number of selected component (if applicable):
qpid-tools-0.18-7.el6_3.noarch


How reproducible:
100%


Steps to Reproduce:
1. Setup and run e.g. 3node HA cluster without using virtual IP.
2. Try to run any qpid-* tool

  
Actual results:
$ qpid-config -b "node1,node2,node3"
Failed: ConnectError: [Errno -2] Name or service not known
$ qpid-config -b "amqp:node1,node2,node3"
Failed: ValueError: amqp:node1,node2,node3
$


Expected results:
Having options of qpid-* tools such that firing one command automatically connects to the active broker.


Additional info:

Comment 2 Red Hat Bugzilla 2025-02-10 03:27:13 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


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