Bug 1088609

Summary:	[GSS] (6.2.x) Implement sync of counters for non transactional sends
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Jimmy Wilson <jawilson>
Component:	HornetQ	Assignee:	Clebert Suconic <csuconic>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Svehla <msvehla>
Severity:	unspecified	Docs Contact:	Lucas Costi <lcosti>
Priority:	unspecified
Version:	6.2.1	CC:	lcosti, msvehla
Target Milestone:	CR2
Target Release:	EAP 6.2.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:
Clones:	1089853 (view as bug list)		Environment:
Last Closed:	2014-06-09 12:48:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1089853
Bug Blocks:	1067532, 1084639

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