Bug 1088599 - [GSS] (6.2.x) ClientConsumer max rate not taking effect if ServerLocator's consumerMaxRate <=0
Summary: [GSS] (6.2.x) ClientConsumer max rate not taking effect if ServerLocator's co...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR2
: EAP 6.2.3
Assignee: Clebert Suconic
QA Contact: Martin Svehla
Lucas Costi
URL:
Whiteboard:
Depends On: 1089835
Blocks: eap62-cp03-blockers 1084639
TreeView+ depends on / blocked
 
Reported: 2014-04-16 20:48 UTC by Jimmy Wilson
Modified: 2014-06-09 12:47 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
: 1089835 (view as bug list)
Environment:
Last Closed: 2014-06-09 12:47:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jimmy Wilson 2014-04-16 20:48:16 UTC 
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 Martin Svehla 2014-05-06 13:50:52 UTC 
Verified with EAP 6.2.3.CP.CR2 / HornetQ 2.3.14.1.Final
Note You need to log in before you can comment on or make changes to this bug.