Bug 1063768 - Expired cache entries are not pruned from memory and store on access
Summary: Expired cache entries are not pruned from memory and store on access
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.1.0,6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-11 12:09 UTC by wfink
Modified: 2018-12-04 17:25 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-14 12:19:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-3997 0 Major Resolved Expired cache entries are not pruned from memory and store on access 2014-04-04 09:19:34 UTC

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
Note You need to log in before you can comment on or make changes to this bug.