Bug 1383945 - Expiration is not working under some circumstances with AtomicMap
Summary: Expiration is not working under some circumstances with AtomicMap
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR1
: 6.6.2
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 1374440
TreeView+ depends on / blocked
 
Reported: 2016-10-12 08:32 UTC by wfink
Modified: 2022-03-03 09:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1715604 0 unspecified CLOSED Review Request: rust-actix-threadpool - Actix thread pool for sync code 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker ISPN-7105 0 Major Resolved Expiration is not working under some circumstances with AtomicMap 2017-09-13 07:05:26 UTC

Description wfink 2016-10-12 08:32:56 UTC 
When AtomicMaps are used with writeskew (+ simple versioning) lifespan from the config file is ignored and instead get infinite lifespan for the entries.

The configured default value is used if I any of the following parameters change

    Disable write skew checks
    Use a normal put (not atomic maps)
    Do not start transactions first.
Note You need to log in before you can comment on or make changes to this bug.