This release of JBoss EAP 6 contains an enhancement with an increase in the number of checks performed to guarantee the page counter is synced properly. This enhancement was added as it was found that, in earlier versions of the product, the page counter could get out of sync between paged messages and what was stored on the journal which could lead to negative delivering numbers. The extra checks prevent this from happening.
+++ This bug was initially created as a clone of Bug #1088609 +++
There's a case where sending non tx messages, persistently, you may get out of sync on the counters with paging in case of a failure
I never consider that a big deal since it would be a small window where the counter would be out of sync... after a failover until the page was completely consumed.. however users are complaining about this.
I have implemented a new record type on page that will be a point of sync when a new counter is on a pending state regarding a page file.
When the page is closed I then remove the pending record and make the cursor effective.
Marked this bug as an Enhancement for Release Notes purposes and set requires_doc_text flag to '-' as issue still open (MODIFIED) at the time of preparing Release Notes for 6.3.0 Beta.
Reformatted Doc Text content for future use in Release Notes documentation.
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