Bug 995001 - Doc: MICG 4.2 queue limit policies flow-to-disk superseded and ring-strict dropped
Summary: Doc: MICG 4.2 queue limit policies flow-to-disk superseded and ring-strict dr...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Installation_and_Configuration_Guide
Version: 3.0
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-08-08 11:49 UTC by Zdenek Kraus
Modified: 2015-08-10 01:23 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Zdenek Kraus 2013-08-08 11:49:02 UTC
Description of problem:
In MRG 2 there were four queue limit policies: reject, flow-to-disk, ring, ring-strict

but in MRG 3 the flow-to-disk is superseded by paged queue feature
and the ring-strict were removed

Version-Release number of selected component (if applicable):
-

How reproducible:
-

Steps to Reproduce:
-

Actual results:
--limit-policy [none, reject, flow-to-disk, ring, ring-strict]	 Action to take when queue limit is reached.

Expected results:
--limit-policy [none, reject, ring]	 Action to take when queue limit is reached.

Additional info:

also the limit policies are mentioned on other places in documentation, and maybe also in the programming guide.

for example 4.11.1. Flow Control

please update those accordingly

Comment 4 Leonid Zhaldybin 2014-01-22 09:34:04 UTC
Looks good, verifying.


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