Bug 1089835 – [GSS] (6.3.0) ClientConsumer max rate not taking effect if ServerLocator's consumerMaxRate <=0

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1089835 - [GSS] (6.3.0) ClientConsumer max rate not taking effect if ServerLocator's consumerMaxRate <=0

Summary:	[GSS] (6.3.0) ClientConsumer max rate not taking effect if ServerLocator's co...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	HornetQ (Show other bugs)
Sub Component:
Version:	6.2.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	DR2
Target Release:	EAP 6.3.0
Assigned To:	Clebert Suconic
QA Contact:	Miroslav Novak
Docs Contact:	Russell Dickenson

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1064596 1084639 1088599
	Show dependency tree / graph

Reported:	2014-04-22 00:30 EDT by Jimmy Wilson
Modified:	2014-08-06 10:35 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	In previosus versions of JBoss EAP 6, the Core API method `createConsumer(String queueName, String filter, int windowSize, int maxRate, boolean browseOnly)` ignored the parameter `maxRate` if the `ConnectionFactory` (or `ServerLocator`) had set `maxRate` to its default value of less than or equal to zero. The root cause of this issue was faulty logic in the `createConsumer` method. It has been corrected in this release.
Story Points:	---
Clone Of:	1088599
Environment:
Last Closed:	2014-08-06 10:35:08 EDT
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 Jimmy Wilson 2014-04-22 00:30:00 EDT

+++ This bug was initially created as a clone of Bug #1088599 +++

If ServerLocator's consumerMaxRate is <= 0 (the default), specifying maxRate with ClientSession.createConsumer() methods that take it makes no difference, maxRate ends up being ignored.

Comment 1 Russell Dickenson 2014-05-13 19:19:56 EDT

I have completed the Release Notes entry for this BZ ticket, based on RN text from BZ1088599.

Comment 2 Kabir Khan 2014-07-01 10:26:30 EDT

Should be fixed by upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1064596 for DR2

Comment 3 Miroslav Novak 2014-07-02 03:38:13 EDT

Verified in EAP 6.3.0.ER7 using provided tests MessageRateTest.

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