Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-7353

Expiration lifespan will not change until server restart if applied by CLI command

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • RHDG 8.5.2 GA
    • RHDG 8.4.7 GA, RHDG 8.4.8 GA
    • Core, Server
    • None
    • False
    • None
    • False
    • Hide

      Start a vanilla server (8.4.8)
      Create a cache using the attached template.
      CLI: create cache --file ProtobufSimpleEntryCache.xml ExpirationCache

       

      Add entries and check that the lifespan is 10seconds

       

      Alter the cache with
      CLI: alter cache ExpirationCache --attribute=expiration.lifespan --value=120000
      Create a new entry and check that the lifespan is still 10sec

      Restart the server
      Create a new entry an check the lifespan is now 120sec

      Show
      Start a vanilla server (8.4.8) Create a cache using the attached template. CLI: create cache --file ProtobufSimpleEntryCache.xml ExpirationCache   Add entries and check that the lifespan is 10seconds   Alter the cache with CLI: alter cache ExpirationCache --attribute=expiration.lifespan --value=120000 Create a new entry and check that the lifespan is still 10sec Restart the server Create a new entry an check the lifespan is now 120sec

      If a cache is created with an expiration lifespan by using CLI and altered after that the change will not take effect until the server is restarted.

      The expectation is that new entries are created with the lifespan applied by the CLI "alter cache" command.

              wburns@redhat.com Will Burns
              rhn-support-wfink Wolf Fink
              Pavel Drobek Pavel Drobek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: