[JBoss JIRA] (ISPN-10640) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-10640?page=com.atlassian.jira.plugin... ]
Will Burns updated ISPN-10640:
------------------------------
Security: (was: Red Hat Internal)
> 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)
5 years, 3 months