Bug 1088609 - [GSS] (6.2.x) Implement sync of counters for non transactional sends
Summary: [GSS] (6.2.x) Implement sync of counters for non transactional sends
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: 1089853
Blocks: eap62-cp03-blockers 1084639
TreeView+ depends on / blocked
 
Reported: 2014-04-16 21:10 UTC by Jimmy Wilson
Modified: 2014-06-09 12:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When sending non-TX messages persistently, the page counter could get out of sync between paged messages and what was stored on the journal, and this could had led to negative delivering numbers. In this release, extra checks were added to guarantee the page counter is synced properly.
Clone Of:
: 1089853 (view as bug list)
Environment:
Last Closed: 2014-06-09 12:48:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jimmy Wilson 2014-04-16 21:10:02 UTC
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.

Comment 1 Martin Svehla 2014-05-06 13:55:54 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.