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.
+++ 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.
I have completed the Release Notes entry for this BZ ticket, based on RN text from BZ1088599.
Should be fixed by upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1064596 for DR2
Verified in EAP 6.3.0.ER7 using provided tests MessageRateTest.