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

Infinispan expiration lifespan max size -1

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 37.0.1.Final
    • Clustering
    • None
    • Hide

      use sample

      standalone-full-ha.xml and modify expirationinterval by adding  
      lifespan=-1 
      as an attribute
       
      <cache-containername="server"default-cache="default"aliases="singleton cluster"modules="org.wildfly.clustering.singleton.server"marshaller="PROTOSTREAM">
      <transportlock-timeout="60000"/>
      <replicated-cachename="default">
      <transactionmode="BATCH"/>
      <expirationinterval="0"/>
      </replicated-cache>
      </cache-container>
       

      Show
      use sample standalone-full-ha.xml and modify expirationinterval by adding   lifespan=-1  as an attribute   <cache-containername="server"default-cache="default"aliases="singleton cluster"modules="org.wildfly.clustering.singleton.server"marshaller="PROTOSTREAM"> <transportlock-timeout="60000"/> <replicated-cachename="default"> <transactionmode="BATCH"/> <expirationinterval="0"/> </replicated-cache> </cache-container>  
    • ---
    • ---

      Upgrading from WildFly 26 to 37 

      subsystem  
      <subsystemxmlns="urn:jboss:domain:infinispan:15.0">
       
      <replicated-cachename="EJB_SESSION_CACHE"remote-timeout="30000"statistics-enabled="true">
      <transactionmode="BATCH"/>
      <lockingisolation="REPEATABLE_READ"/>
      <heap-memorysize="-1"/>
      <expirationinterval="60000"lifespan="-1"max-idle="7200000"/>
      <state-transferchunk-size="512"timeout="120000"/>
      </replicated-cache>
       
      we are trying to create an expiration internval that doesn't expire 
      https://docs.wildfly.org/37/wildscribe/subsystem/infinispan/cache-container/replicated-cache/component/expiration/index.html
       

      • lifespan Maximum lifespan of a cache entry, after which the entry is expired cluster-wide, in milliseconds. -1 means the entries never expire.

      yet  we see this issue
      A minimum value of 0 is required
      OPVDX001: Validation error in standalone.xml -----------------------------------

       623:         <transaction mode="BATCH"/>
       624:         <heap-memory size="100000"/>
       625:         <expiration interval="60000" lifespan="-1" max-idle="7200000"/>
                                                                                   ^^^^ -1 is an invalid value for parameter lifespan. A minimum value of 0 is
                                                                                          required
       626:         <state-transfer chunk-size="512" timeout="120000"/>
       627:     </replicated-cache>
       628: </cache-container>
      The primary underlying error message was:
      > ParseError at [row,col]:[625,84]
      > Message: "WFLYCTL0117: -1 is an invalid value for parameter lifespan.
      >   A minimum value of 0 is required"
       
       
      Attribute Value
      Type LONG
      Nillable true
      Expressions Allowed true
      Min 0
      Max -1
      Unit MILLISECONDS
      Storage configuration
      Access Type read-write
      Restart Required resource-services
      Stability default

       

      As an aside, I tried to check if this is the same in 38 but the 

              pferraro@redhat.com Paul Ferraro
              srchl Sergio loza
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: