Bug 1383945 - Expiration is not working under some circumstances with AtomicMap
Summary: Expiration is not working under some circumstances with AtomicMap
Keywords:
Status: CLOSED UPSTREAM
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: 2025-02-10 03:49 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:49:20 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


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.
Comment 4 Red Hat Bugzilla 2025-02-10 03:49:20 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.