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

Incorrect settings [timeToLiveSeconds,maxIdleTimeSeconds] when default in REST

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Deferred
    • 5.1.0.ALPHA1
    • None
    • Remote Protocols
    • None
    • Hide

      Start a infinispan REST server
      Configure cache with <expiration lifespan="30000" maxIdle="30000" />
      POST a new entry without maxIdleTimeSeconds or timeToLiveSeconds HTTP header
      This new entry will survive all the time.

      Show
      Start a infinispan REST server Configure cache with <expiration lifespan="30000" maxIdle="30000" /> POST a new entry without maxIdleTimeSeconds or timeToLiveSeconds HTTP header This new entry will survive all the time.
    • Workaround Exists
    • Hide

      As indicated in the API documentation, you can get entries to be stored with configured expiration/lifespan settings passing 0 as parameters:
      https://docs.jboss.org/author/display/ISPN/Accessing+data+in+Infinispan+via+RESTful+interface

      Show
      As indicated in the API documentation, you can get entries to be stored with configured expiration/lifespan settings passing 0 as parameters: https://docs.jboss.org/author/display/ISPN/Accessing+data+in+Infinispan+via+RESTful+interface
    • Low

    Description

      If HTTP client didn't use
      timeToLiveSeconds or/and maxIdleTimeSeconds in all PUT/POST header request
      Cache entry will allways use -1 for timeToLiveSeconds and -1 for maxIdleTimeSeconds
      instead of current Cache settings

      Attachments

        Issue Links

          Activity

            People

              gzamarre Galder ZamarreƱo
              rh-gs-gautric Greg A. (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2 hours
                  2h
                  Remaining:
                  Remaining Estimate - 2 hours
                  2h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified