Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-9519

default values in org.infinispan.configuration.cache.ExpirationConfiguration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 11.0.0.Beta1, 11.0.0.CR1, 11.0.0.Final
    • Clustering
    • None
    • Hide

      Lets assume that we have custom infinispan configuration applied by cli:

      batch
      set ccc=/subsystem=infinispan/cache-container=custom-cache-container
      $ccc:add(default-cache=custom-cache)
      $ccc/transport=TRANSPORT:add()
      $ccc/replicated-cache=custom-cache:add(mode=SYNC)                                                                                             
      $ccc/replicated-cache=custom-cache/expiration=EXPIRATION:add(max-idle=33, lifespan=66, interval=88)
      run-batch
      :reload

      and check how org.infinispan.configuration.cache.ExpirationConfiguration was settled:

      @Stateless
      @Path("/")
      public class Showcase {
      
        @Resource(lookup = "java:jboss/infinispan/container/custom-cache-container")
        private EmbeddedCacheManager cacheContainer;
      
        @GET
        @Path("/expiration")
        public String expiration() {
          return "" + cacheContainer.getCache()
              .getCacheConfiguration()
              .expiration() + "\n";
        }
      
      }
      

      I made a simple demo to help us:

      ./showcase.sh 11.0.0.Final
      expected result
      ExpirationConfiguration [attributes=[wakeUpInterval=88, maxIdle=33, reaperEnabled=true, lifespan=66]]
      
      actual result
      ExpirationConfiguration [attributes=[wakeUpInterval=60000, maxIdle=-1, reaperEnabled=true, lifespan=-1]]
      

      finally, I compared last five releases:

      • 10.1.0.Final - Passed
      • 11.0.0.Alpha1 - Passed
      • 11.0.0.Beta1 - Regression
      • 11.0.0.CR1 - Regression
      • 11.0.0.Final - Regression

      It seems to me that someone made regression in WildFly 11.0.0.Beta1

      Show
      Lets assume that we have custom infinispan configuration applied by cli: batch set ccc=/subsystem=infinispan/cache-container=custom-cache-container $ccc:add( default -cache=custom-cache) $ccc/transport=TRANSPORT:add() $ccc/replicated-cache=custom-cache:add(mode=SYNC) $ccc/replicated-cache=custom-cache/expiration=EXPIRATION:add(max-idle=33, lifespan=66, interval=88) run-batch :reload and check how org.infinispan.configuration.cache.ExpirationConfiguration was settled: @Stateless @Path( "/" ) public class Showcase { @Resource(lookup = "java:jboss/infinispan/container/custom-cache-container" ) private EmbeddedCacheManager cacheContainer; @GET @Path( "/expiration" ) public String expiration() { return "" + cacheContainer.getCache() .getCacheConfiguration() .expiration() + "\n" ; } } I made a simple demo to help us: ./showcase.sh 11.0.0.Final expected result ExpirationConfiguration [attributes=[wakeUpInterval=88, maxIdle=33, reaperEnabled= true , lifespan=66]] actual result ExpirationConfiguration [attributes=[wakeUpInterval=60000, maxIdle=-1, reaperEnabled= true , lifespan=-1]] finally, I compared last five releases: 10.1.0.Final - Passed 11.0.0.Alpha1 - Passed 11.0.0.Beta1 - Regression 11.0.0.CR1 - Regression 11.0.0.Final - Regression It seems to me that someone made regression in WildFly 11.0.0.Beta1

      I had noticed regression issue in WildFly's Infinispan submodule. Object of class org.infinispan.configuration.cache.ExpirationConfiguration always contains default values.

              pferraro@redhat.com Paul Ferraro
              metempsychoza R O (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: