Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1124718

Summary:	JDG640.ClusteredListeners
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Tristan Tarrant <ttarrant>
Component:	Library	Assignee:	William Burns <wburns>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Gencur <mgencur>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	jdg-bugs
Target Milestone:	DR1
Target Release:	6.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-28 13:31:13 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:
Bug Blocks:	1124710

Description Tristan Tarrant 2014-07-30 07:28:09 UTC

Requirement:
	

Notify client applications when an entry is added, updated, deleted, or expired in a particular cache. Event should be cluster-wide, so that client applications can (a) access this event regardless of which node the app resides on or connects with and (b) the app receives a single notification per event.

Priority:
	

P1

Status:
	

Committed

Originator:
	

Product Management

Responsible team:
	

Infinispan Engineering Team

Comments:
	

a) the event will be triggered always on the node where the listener was registered, but disregarding where the cache update originated

b) is not possible for the app to receive a single notification per event due to technical reasons during topology changes. However the window for which this happens is quite small

c) expiry events won’t be covered, the others will

Attachments:
	

Clustered listeners · infinispan/infinispan Wiki · GitHub

Interdependencies:

Comment 2 Martin Gencur 2014-11-19 12:48:24 UTC

This feature was deliver a long time ago. New issues will be filed in separate BZs.