[
https://issues.jboss.org/browse/ISPN-10640?page=com.atlassian.jira.plugin...
]
Will Burns commented on ISPN-10640:
-----------------------------------
This is caused by the fact that we don't have a way to specify the created or last
used values when adding an entry into memory.
https://github.com/infinispan/infinispan/blob/bd580e6254c1fc7c6cda4e43e45...
for example has the created and maxIdle available in the marshalled entry, but this is not
passed into the cache.
If Expiration is enabled the cretionDate is modified to the current
server start date if preload is enabled for a persistence
-----------------------------------------------------------------------------------------------------------------------------
Key: ISPN-10640
URL:
https://issues.jboss.org/browse/ISPN-10640
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 9.4.16.Final
Environment: Cache configuration with preload
<local-cache name="default">
<persistence>
<file-store shared="false" preload="true"
fetch-state="true"/>
</persistence>
</local-cache>
Reporter: Will Burns
Assignee: Will Burns
Priority: Critical
If a cache store entries with expiration the MetaData creationTime is used to calculate
the expiration.
This works correct if the server is not restarted or preload=false for the store.
If preload is enabled and the server preload the date the creationTime is set to the
current server start time.
In this case all expiration for existing entries is not working correctly
--
This message was sent by Atlassian Jira
(v7.13.8#713008)