In previous versions of JBoss EAP 6, the client consumer would ack messages individually in certain scenarios, for example after failures. This process was very inefficient.
This issue has been addressed in this release.
+++ This bug was initially created as a clone of Bug #1088616 +++
Should be fixed by upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1064596 for DR2
Verified in EAP 6.3.0.ER7 / HornetQ 2.3.19.Final