[infinispan-issues] [JBoss JIRA] (ISPN-10618) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence

[Will Burns (Jira)]

     [ https://issues.jboss.org/browse/ISPN-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Burns updated ISPN-10618:
------------------------------
    Fix Version/s: 10.0.0.CR3
                   9.4.17.Final


> If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-10618
>                 URL: https://issues.jboss.org/browse/ISPN-10618
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Loaders and Stores
>    Affects Versions: 10.0.0.CR2
>         Environment: Cache configuration with preload
>                 <local-cache name="default">
>                  <persistence>
>                     <file-store shared="false" preload="true" fetch-state="true"/>
>                  </persistence>
>                 </local-cache>
>            Reporter: Wolf-Dieter Fink
>            Assignee: Will Burns
>            Priority: Blocker
>             Fix For: 10.0.0.CR3, 9.4.17.Final
>
>
> 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)