Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 506420 - qpid-config -h does not explain exchange type
qpid-config -h does not explain exchange type
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: python-qpid (Show other bugs)
1.1.1
All Linux
low Severity low
: 1.3
: ---
Assigned To: Ted Ross
Frantisek Reznicek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-17 04:55 EDT by Frantisek Reznicek
Modified: 2015-11-15 19:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The usage information for the qpid-config utility (that is, the output of the "qpid-config -h" command) have been updated to include a brief explanation of the exchange type.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-14 11:58:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0773 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Messaging and Grid Version 1.3 2010-10-14 11:56:44 EDT

  None (edit)
Description Frantisek Reznicek 2009-06-17 04:55:33 EDT
Description of problem:
The qpid-config python client from python-qpid package does not explain (even shortly) which type can be used for declating exchange, i.e. command
qpid-config [OPTIONS] add exchange <type> <name> [AddExchangeOptions]
                                   ^^^^^^ not clear

It would be beneficial to add one or two lines on that to qpid-config help.

Version-Release number of selected component (if applicable):
python-qpid-0.5.752581-3.el5, python-qpid-0.5.760500-4.el4

How reproducible:
100%

Steps to Reproduce:
1. qpid-config -h
  
Actual results:
In 'qpid-config [OPTIONS] add exchange <type> <name> ...'
<type> field not explained in qpid-config -h

Expected results:
<type> field should be shortly explained in qpid-config -h

Additional info:
[root@dhcp-lab-200 ~]# rpm -q python-qpid
python-qpid-0.5.752581-3.el5
[root@dhcp-lab-200 ~]# qpid-config -h
Usage:  qpid-config [OPTIONS]
        qpid-config [OPTIONS] exchanges [filter-string]
        qpid-config [OPTIONS] queues    [filter-string]
        qpid-config [OPTIONS] add exchange <type> <name> [AddExchangeOptions]
        qpid-config [OPTIONS] del exchange <name>
        qpid-config [OPTIONS] add queue <name> [AddQueueOptions]
        qpid-config [OPTIONS] del queue <name>
        qpid-config [OPTIONS] bind   <exchange-name> <queue-name> [binding-key]
        qpid-config [OPTIONS] unbind <exchange-name> <queue-name> [binding-key]

Options:
    --timeout seconds (10)                    Maximum time to wait for broker connection
    -b [ --bindings ]                         Show bindings in queue or exchange list
    -a [ --broker-addr ] Address (localhost)  Address of qpidd broker
         broker-addr is in the form:   [username/password@] hostname | ip-address [:<port>]
         ex:  localhost, 10.1.1.7:10000, broker-host:10000, guest/guest@localhost

Add Queue Options:
    --durable            Queue is durable
    --cluster-durable    Queue becomes durable if there is only one functioning cluster node
    --file-count N (8)   Number of files in queue's persistence journal
    --file-size  N (24)  File size in pages (64Kib/page)
    --max-queue-size N   Maximum in-memory queue size as bytes
    --max-queue-count N  Maximum in-memory queue size as a number of messages
    --limit-policy [none | reject | flow-to-disk | ring | ring-strict]
                         Action taken when queue limit is reached:
                             none (default) - Use broker's default policy
                             reject         - Reject enqueued messages
                             flow-to-disk   - Page messages to disk
                             ring           - Replace oldest unacquired message with new
                             ring-strict    - Replace oldest message, reject if oldest is acquired
    --order [fifo | lvq | lvq-no-browse]
                         Set queue ordering policy:
                             fifo (default) - First in, first out
                             lvq            - Last Value Queue ordering, allows queue browsing
                             lvq-no-browse  - Last Value Queue ordering, browsing clients may lose data
    --generate-queue-events N
                         If set to 1, every enqueue will generate an event that can be processed by
                         registered listeners (e.g. for replication). If set to 2, events will be
                         generated for enqueues and dequeues

Add Exchange Options:
    --durable    Exchange is durable
    --sequence   Exchange will insert a 'qpid.msg_sequence' field in the message header
                 with a value that increments for each message forwarded.
    --ive        Exchange will behave as an 'initial-value-exchange', keeping a reference
                 to the last message forwarded and enqueuing that message to newly bound
                 queues.
Comment 1 Ted Ross 2009-08-25 16:58:36 EDT
Fixed upstream at revision 807802.
Comment 3 Frantisek Reznicek 2010-07-27 04:27:32 EDT
The issue is resolved in qpid-config help for RHEL 4.8 / 5.5 i386 / x86_64 in packages: qpid-tools-0.7.946106-7.el4/5

-> VERIFIED
Comment 4 Jaromir Hradilek 2010-10-07 09:21:14 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The usage information for the qpid-config utility (that is, the output of the "qpid-config -h" command) have been updated to include a brief explanation of the exchange type.
Comment 6 errata-xmlrpc 2010-10-14 11:58:30 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0773.html

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