OK, I'll try tagging all topics that contain queue and exchange declaration arguments with a common tag as I go.

Then I'll query for them, and collate them into topic 8380, then circle back with the completed list to ask what's missing.

Setting devel conditional NAK -- this bug will be fixed if information is provided by 30 November, otherwise we'll have to push it to the next release. Setting needinfo to Justin, please and thank you!

Use this site:
  https://cwiki.apache.org/confluence/display/qpid/Qpid+extensions+to+AMQP
to see explanatory comments on most Queue and Exchange args.


I have gathered all of them here, including some that are not
documented on that page.

I've given the data types for each one, and included explanatory
comments for those few that are not already commented on the
above wiki page.

I also have notes associated with a few of the arguments, when
there's something unusual going on.


NOTE: You may or may not want to not document the queue arg
      'qpid.insert_sequence_numbers'.  The comment in the code
      says that it is not completely ready for prime-time.




EXCHANGE arguments
{
  -------------------------------------------
  NAME: qpid.msg_sequence
  {
    type : bool

    comment: Causes the exchange to insert a sequence number
             in the header of each message, at key "qpidMsgSequence".
  }

  -------------------------------------------
  NAME: qpid.ive
  {
    type : bool
  }

  -------------------------------------------
  NAME: qpid.sequence_counter
  {
    type: int64

    comment: Start qpid.msg_sequence counting at the given number.
  }
}





QUEUE arguments
{
  -------------------------------------------
  NAME: no-local
  {
    type : bool
    note : This one has a hyphen.  Most have underbars.
           Also, this is the only one that does not
           begin with the 'qpid.' prefix.
  }

  -------------------------------------------
  NAME: qpid.alert_count
  {
    type : uint32_t
  }

  -------------------------------------------
  NAME: qpid.alert_repeat_gap
  {
    type : int64_t
  }

  -------------------------------------------
  NAME: qpid.alert_size
  {
    type : int64_t
  }

  -------------------------------------------
  NAME: qpid.auto_delete_timeout
  {
    type : bool
  }

  -------------------------------------------
  NAME: qpid.browse-only
  {
    type : bool
    note : This one has a hyphen.  Most have underbars.
           ( The person who wrote the code for this one was kind of dense. )
  }

  -------------------------------------------
  NAME: qpid.file_count
  {
    type : int
  }

  -------------------------------------------
  NAME: qpid.file_size
  {
    type : int64
  }

  -------------------------------------------
  NAME: qpid.flow_resume_count
  {
    type : uint32_t
  }

  -------------------------------------------
  NAME: qpid.flow_resume_size
  {
    type : uint64_t
  }

  -------------------------------------------
  NAME: qpid.flow_stop_count
  {
    type : uint32_t
  }

  -------------------------------------------
  NAME: qpid.flow_stop_size
  {
    type : uint64_t
  }

  -------------------------------------------
  NAME: qpid.insert_sequence_numbers
  {
    type:   string

    comment
    {
      Feature is not ready for general use as it doesn't
      handle the case where a message is enqueued on more
      than one queue well enough.
    }

    note
    {
      valid values:  "qpid.replication.seqno"
    }
  }

  -------------------------------------------
  NAME: qpid.last_value_queue
  {
    type : bool
  }

  -------------------------------------------
  NAME: qpid.last_value_queue_key
  {
    type : string
  }

  -------------------------------------------
  NAME: qpid.last_value_queue_no_browse
  {
    type : bool
  }

  -------------------------------------------
  NAME: qpid.max_count
  {
    type : uint32_t
  }

  -------------------------------------------
  NAME: qpid.max_size
  {
    type : int64_t
  }

  -------------------------------------------
  NAME: qpid.msg_sequence
  {
    type : bool
  }

  -------------------------------------------
  NAME: qpid.persist_last_node
  {
    type:    bool
    comment: If a cluster has broker failures that reduce it to a
             single node, the queue should make its data persistent.
  }

  -------------------------------------------
  NAME: qpid.policy_type
  {
    type : string
  }

  -------------------------------------------
  NAME: qpid.priorities
  {
    type : size_t
  }

  -------------------------------------------
  NAME: qpid.queue_event_generation
  {
    type : int
    note : valid values: ENQUEUE_ONLY=1 ENQUEUE_AND_DEQUEUE=2
  }

  -------------------------------------------
  NAME: qpid.trace.exclude
  {
    type : string
    note : comma-separated list of messages to exclude
  }

  -------------------------------------------
  NAME: qpid.trace.id
  {
    type : string
  }

}

Thanks Mick, I've documented the ones you've given.

On the wiki page are these three marked as "Y" for C++. Should they also go into the list?

x-qpid-maximum-message-size	
x-qpid-maximum-message-count	
x-qpid-minimum-alert-repeat-gap

Yes, they are there -- but it looks like they are all aliases for other names.

x-qpid-maximum-message-size     is an alias for qpid.alert_size
x-qpid-maximum-message-count    is an alias for qpid.alert_count
x-qpid-minimum-alert-repeat-gap is an alias for qpid.alert_repeat_gap

I have incorporated the three remaining arguments.

http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html-single/Messaging_Installation_and_Configuration_Guide/index.html#Exchange_and_Queue_Argument_Reference1

Hi Joshua, just a very minor issue here. You have decided to describe also the aliases mentioned in comment 12,  but you've omitted one (marked on the wiki page with "Y" for C++ as well):

x-qpid-priorities is an alias for qpid.priorities

http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html-single/Messaging_Installation_and_Configuration_Guide/index.html#Exchange_and_Queue_Argument_Reference1

Docs published on https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_MRG/