Description of problem:


MRG 2.0 Msg User's Guide, Chapter 3, Configuring queue options:

The output given for the "qpid-config queues" command is very out-of-date.

For 2.0, the output now appears as:

<begin>
$ qpid-config queues
Queue Name                                Attributes
=================================================================
my-queue                                  --durable 
qmfc-v2-hb-localhost.localdomain.20293.1  auto-del excl --limit-policy=ring 
qmfc-v2-localhost.localdomain.20293.1     auto-del excl 
qmfc-v2-ui-localhost.localdomain.20293.1  auto-del excl --limit-policy=ring 
reply-localhost.localdomain.20293.1       auto-del excl 
topic-localhost.localdomain.20293.1       auto-del excl --limit-policy=ring 
<end>

In addition, the options listed for creating queues are out of date - some have changed names and new options are available for 2.0.  The 2.0 option set is:

<begin>

    --alternate-exchange=<aexname>
                        Name of the alternate-exchange for the new queue or
                        exchange. Exchanges route messages to the alternate
                        exchange if they are unable to route them elsewhere.
                        Queues route messages to the alternate exchange if
                        they are rejected by a subscriber or orphaned by queue
                        deletion.
    --passive, --dry-run
                        Do not actually add the exchange or queue, ensure that
                        all parameters and permissions are correct and would
                        allow it to be created.
    --durable           The new queue or exchange is durable.

    --cluster-durable   The new queue becomes durable if there is only one
                        functioning cluster node
    --file-count=<n>    Number of files in queue's persistence journal
    --file-size=<n>     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=<policy>
                        Action to take when queue limit is reached
    --order=<ordering>  Queue ordering policy
    --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.
    --flow-stop-size=<n>
                        Turn on sender flow control when the number of queued
                        bytes exceeds this value.
    --flow-resume-size=<n>
                        Turn off sender flow control when the number of queued
                        bytes drops below this value.
    --flow-stop-count=<n>
                        Turn on sender flow control when the number of queued
                        messages exceeds this value.
    --flow-resume-count=<n>
                        Turn off sender flow control when the number of queued
                        messages drops below this value.
    --argument=<NAME=VALUE>
                        Specify a key-value pair to add to queue arguments


<end>