Bug 1272052 - Expiration does not work correct in C/S mode for a cache if putIfAbsent(K,V) is used
Summary: Expiration does not work correct in C/S mode for a cache if putIfAbsent(K,V) ...
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan, Server
Version: 6.5.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER1
: 6.6.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-15 11:09 UTC by wfink
Modified: 2023-09-30 08:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Expiration settings of a cache were ignored in JBoss Data Grid server if <methodname>putIfAbsent</methodname> operation was invoked via HotRod client. This could lead to wrong assumptions about presence of an entry in the cache, which never expired. The issue is resolved as of Red Hat JBoss Data Grid 6.6.0. The entry correctly expires after predefined time period.
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-5863 0 Critical Resolved Default metadata not merged for DecoratedCache operations 2016-03-08 04:01:00 UTC
Red Hat Issue Tracker ISPN-5877 0 Major Resolved PutAll requests can't use skip cache load and skip indexing flags 2016-03-08 04:01:00 UTC

Description wfink 2015-10-15 11:09:26 UTC 
Description of problem:
If the expiration is configured in the server configuration for a cache the entries will not expire as this is the case if the lifespan/maxIdle is set with the put command.
Comment 2 JBoss JIRA Server 2015-10-19 05:53:08 UTC 
Galder Zamarreño <galder.zamarreno> updated the status of jira ISPN-5863 to Coding In Progress
Note You need to log in before you can comment on or make changes to this bug.