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

Bug 1272052

Summary:	Expiration does not work correct in C/S mode for a cache if putIfAbsent(K,V) is used
Product:	[JBoss] JBoss Data Grid 6	Reporter:	wfink
Component:	Infinispan, Server	Assignee:	Tristan Tarrant <ttarrant>
Status:	CLOSED UPSTREAM	QA Contact:	Martin Gencur <mgencur>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.5.1	CC:	chuffman, galder.zamarreno, jdg-bugs
Target Milestone:	ER1
Target Release:	6.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:48:18 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 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

Comment 8 Red Hat Bugzilla 2025-02-10 03:48:18 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.