Bug 885176 – max-connections=0 should disable connection limits

Bug 885176 - max-connections=0 should disable connection limits

Summary:	max-connections=0 should disable connection limits

Status:	NEW

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	qpid-cpp (Show other bugs)
Sub Component:
Version:	2.3
Hardware:	Unspecified Unspecified

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Chuck Rolke
QA Contact:	MRG Quality Engineering
Docs Contact:

URL:
Whiteboard:
Keywords:	Improvement

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-12-07 11:44 EST by Justin Ross
Modified:	2013-02-23 07:14 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Justin Ross 2012-12-07 11:44:36 EST

From Chuck's comment on bug 852572:

"""
QA has observed that setting "--max-connections N" to zero does not disable connection counting. Instead it limits the number of connections allowed to zero rendering the broker useless. 

To disable "--max-connections" the user may set it to a large value like 20000 that is a legal number but is unattainable for other reasons.
"""

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