Bug 1222995

Summary: JSR-107 - Provide mechanism to handle expiration events
Product: [JBoss] JBoss Data Grid 6 Reporter: Matej Čimbora <mcimbora>
Component: InfinispanAssignee: Tristan Tarrant <ttarrant>
Status: CLOSED UPSTREAM QA Contact: Martin Gencur <mgencur>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: chuffman, jdg-bugs
Target Milestone: ER4   
Target Release: 6.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When using a cache configured with expiration in remote JCache implementation, expiration events were not handled in clustered environment on cache <literal>c1</literal>, if the insertion of an entry was performed by cache <literal>c2</literal>. As a consequence, cache entry listener registered on cache <literal>c1</literal> was not notified of the expiration event. The issue is resolved as of Red Hat JBoss Data Grid 6.6.0, and cache entry listeners receive expiration events correctly in clustered environment.
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:47:38 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:

Description Matej Čimbora 2015-05-19 14:48:47 UTC
See details in JIRA.

Note: Not covered by TCK tests.

Comment 2 JBoss JIRA Server 2015-12-03 18:07:28 UTC
Gustavo Fernandes <gustavo> updated the status of jira ISPN-5482 to Reopened

Comment 6 Red Hat Bugzilla 2025-02-10 03:47:38 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.