Description of problem: This will include the fixes from https://bugzilla.redhat.com/show_bug.cgi?id=1057330 and this following fix: https://bugzilla.redhat.com/show_bug.cgi?id=1063864 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Tag created: HornetQ_2_3_16_Final
The solution for https://issues.jboss.org/browse/EAP6-78 (Or the HornetQ part of that issue) is also going to require a change within HornetQ. Currently being implemented under the following issue: - https://issues.jboss.org/browse/HORNETQ-1329 The commits are ready, just need some verification before I send over the pull requests.
I think this is going to need to be 2.3.17 to pick up the now merged changes for EAP6-78
I have tagged HornetQ_2_3_17_Final... do we need a BugZilla for HORNETQ-1329 or the EAP6-78 JIRA covers this? also: There are two other minor fixes that I don't think will need a BZ... HORNETQ-1328 - totalIterator was throwing the paging order first. this would only affect users calling listMessages on the console. HORNETQ-910 - maxRate on the core-api createConsumer was not being honored. this was a typo that is not affecting JMS use cases, which we fixed on the branch to avoid future issues.
https://github.com/jbossas/jboss-eap/pull/978
Verified. HornetQ to 2.3.17.Final is in EAP 6.3.0.DR2. Thanks to all involved!
Clebert Suconic <clebert.suconic> updated the status of jira HORNETQ-1329 to Closed
Clebert Suconic <clebert.suconic> updated the status of jira HORNETQ-1329 to Reopened