Bug 1088599
| Summary: | [GSS] (6.2.x) ClientConsumer max rate not taking effect if ServerLocator's consumerMaxRate <=0 | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jimmy Wilson <jawilson> | |
| Component: | HornetQ | Assignee: | Clebert Suconic <csuconic> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Svehla <msvehla> | |
| Severity: | unspecified | Docs Contact: | Lucas Costi <lcosti> | |
| Priority: | unspecified | |||
| Version: | 6.2.1 | CC: | lcosti, msvehla | |
| Target Milestone: | CR2 | |||
| Target Release: | EAP 6.2.3 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
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. This issue has been fixed in this release of JBoss EAP 6, and the `createConsumer` method now correctly uses the `maxRate` parameter even if it is set to its default value.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1089835 (view as bug list) | Environment: | ||
| Last Closed: | 2014-06-09 12:47:03 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1089835 | |||
| Bug Blocks: | 1067532, 1084639 | |||
|
Description
Jimmy Wilson
2014-04-16 20:48:16 UTC
Verified with EAP 6.2.3.CP.CR2 / HornetQ 2.3.14.1.Final |