Bug 1011384 - MPR: LVQ deprecated arguments
Summary: MPR: LVQ deprecated arguments
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference
Version: 2.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 3.0
: ---
Assignee: Jared MORGAN
QA Contact: Eric Sammons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-24 07:48 UTC by Leonid Zhaldybin
Modified: 2015-08-10 01:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1011381
Environment:
Last Closed: 2015-01-22 15:28:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1011381 0 unspecified CLOSED MCIG: LVQ deprecated arguments 2021-02-22 00:41:40 UTC

Internal Links: 1011381

Description Leonid Zhaldybin 2013-09-24 07:48:07 UTC
+++ This bug was initially created as a clone of Bug #1011381 +++

Description of problem:

MCIG contains the description of two arguments for last value queues: "qpid.last_value_queue (bool)" and "qpid.last_value_queue_no_browse (bool)" in appendix A
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_MRG/2/html-single/Messaging_Installation_and_Configuration_Guide/index.html#appe-Exchange_and_Queue_Declaration_Arguments

These two options are deprecated, see for example http://qpid.apache.org/releases/qpid-0.18/books/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html chapter "1.6.4. Deprecated LVQ Modes". Also, the qpidd broker logs the following warning message if "qpid.last_value_queue_no_browse" argument is used while creating a queue: "[Broker] warning Ignoring 'no-browse' directive for LVQ; it is no longer necessary".

I think the description of the deprecated arguments should be removed from the documentation.

Comment 3 Leonid Zhaldybin 2013-10-03 08:26:01 UTC
The deprecated LVQ options description has been removed from Messaging Programming Reference.

-> VERIFIED


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