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

Bug 1063768

Summary: Expired cache entries are not pruned from memory and store on access
Product: [JBoss] JBoss Data Grid 6 Reporter: wfink
Component: InfinispanAssignee: Tristan Tarrant <ttarrant>
Status: CLOSED NOTABUG QA Contact: Martin Gencur <mgencur>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0, 6.2.0CC: jdg-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-14 12:19:49 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 wfink 2014-02-11 12:09:40 UTC 
Due to the documentation [1] expired entries are pruned by having a scheduler or if they are accessed after expiration.
This will not be done if the key is access.
In case of having no scheduler to prune the entries this might cause OutOfMemory issues.


[1] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Data_Grid/6.2/html/Administration_and_Configuration_Guide/Cache_Entry_Expiration_Notifications.html
Comment 1 JBoss JIRA Server 2014-02-14 11:56:26 UTC 
Mircea Markus <mmarkus> updated the status of jira ISPN-3997 to Resolved
Comment 2 wfink 2014-02-14 12:19:49 UTC 
As stated in ISPN-3997 this is not a bug.
In this case the JDG documentation is wrong and needs to changed.

See https://bugzilla.redhat.com/show_bug.cgi?id=1065341