Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-10640

Expiration creation/lastUsed timestamp are lost when preloading from store

XMLWordPrintable

    • Hide

      Use a vanilla server and add a file-store persistence with preload=true to the default cache

      Add an entry
      echo "lifetime entry" | curl v -uwfink:wfink+42 -X PUT -d @ -H "timetoliveseconds: 10000" --header "Content-Type: text/plain" http://localhost:8080/rest/default/1

      read the entry
      curl -v -uwfink:wfink+42 -o - --header 'Accept: text/plain' http://localhost:8080/rest/default/1

      check the output for creation, modified and expire date
      restart the server
      check again and see the values are changed

      • if preload is set to false the dates are back to correct!

      < created:
      < Expires:
      < Last-Modified:

      Show
      Use a vanilla server and add a file-store persistence with preload=true to the default cache Add an entry echo "lifetime entry" | curl v -uwfink:wfink+42 -X PUT -d @ -H "timetoliveseconds: 10000" --header "Content-Type: text/plain" http://localhost:8080/rest/default/1 read the entry curl -v -uwfink:wfink+42 -o - --header 'Accept: text/plain' http://localhost:8080/rest/default/1 check the output for creation, modified and expire date restart the server check again and see the values are changed if preload is set to false the dates are back to correct! < created: < Expires: < Last-Modified:

      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

              wburns@redhat.com Will Burns
              wburns@redhat.com Will Burns
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: